2.need to add some launh condition if the user machine doesn't has Crystal Report for 2008 and Chat controls for .Net 3.5 SP1 i make the project to instal the things first then install the project how to do this
I'd like to implement a ADO.NET/WCF DataService and I am wondering what's the best way to setup a project in VS2008 SP1 for this purpose.
Currently I have an ASP.NET web application project (not of "WebSite" project type). The data access layer is an Entity model (EF version 1) with SQL Server database. I have the Entity Model in a separate DLL project and the web application project references to this assembly for all data accesses.
The ADO.NET/WCF DataService needs to communicate with the Entity model/database as well. It has to be hosted on the same web server (IIS 7.5) together with the web application.
Since the DataService is not directly related to that specific web application (though it will provide and modify data from/in the same database the web application uses as well) my basic idea was to separate the DataService in its own new project (which also references the Entity Model DLL).
Now I have seen that there is no project type "ADO.NET/WCF DataService" in VS2008 SP1. It seems only possible to add a DataService as an element to other existing projects, for instance Web Application projects.
Why isn't there a separate DataService project type? Does this mean now that I have to add the DataService as an element to my Web Application project? Or shall I create a new Web Application project and add a DataService to it? (I could delete the pregenerated default.aspx since I do not need any web pages in this project.)
In one asp.net project, I created a setup project. It is working fine. Is it possible to add SQL scripts(to create database and store procedures) into setup project and run scripts automatically once client user installs the application?
edit I do not want to redirect pages, specific files etc. I would like to change the path where images, videos and other media are stored from the root source directory to the directory of my choosing. In this case c:/dev/prjfiles/prjname/public (c:/dev/prjfiles/prjname/ is my working directory) and i except when my html does img src="/pic.png" it will find the image in c:/dev/prjfiles/prjname/publi/pic.png. I need a working solution, i tried looking at how to set virtual directories and etc. I cant figure it out.
I'm trying to figure out the best approach to architecting this project. Basically, it's a "band" profile site. I'm using ASP.NET 4, EF, and Automapper (structuremap too, but that's not important). I'm running into performance issues I have a EntityFramework repository class that interacts directly onto the EF objects using LINQ:
[Pluggable("Repository")] public class EntityDataRepository : IRepository static EntityDataRepository() // other mappings removed // Data. objects are EF objects, mapping to my DTO classes [code]...
i created a web setup project for my asp.net application. am trying to create an upgrade MSI that will only replace some few files in my initial installation (very minor upgrade). right now, am not getting it right because the whole initial set of files is been replaced. i guess i only need to change the package code, but i cant do this in VS.NET 2008.
When I open up a web application project, VS attemps to configure IIS to open the project. This is fine, but typically there is already an application in that place. For example, we have apps that run at the root, and various feature branches would map to the same virtual application. Even though VS can *create* the application, it won't modify an existing one.
For example, lets say IIS has: /MyApp During my day I mightwant to work on MyApp from: c:ranchesfeature1MyApp c:ranchesfeature2MyApp c:archive elease102MyApp c:production elease204MyApp
If I delete /MyApp, then VS will create it when I open any of these projects, but it will never modify /MyApp to point to my current project. So first thing is: Is there any way to change this behavior?
Second question is, is there no way to open a web application project w/o having a properly backed IIS application setup? I know you can have the projects run off the casini webserver, but all of our applications target IIS and rely on inherited web.config settings. /MyApp is expecting to find config values that exist at /Web.Config and a login page for the entire system at /Login.aspx. Trying to run /MyApp in casini fails immediately because of these dependencies.
But what if I am just doing a code review. I don't care to browse the site, I just want to open the project. Is there no way to tell VS to just open the project and ignore the fact that IIS isn't setup right?
I am not new to ASP.Net application development but I haven't used some of the new frameworks or features that are used in applications these days.
For cross-cutting concerns, things like: Logging, Caching and DAAB are used in projects these days to implement proven and efficient source code from either Microsoft or other third party vendors such as Log4Net for logging purposes.
is it possible to create a Setup project within Visual Studio that will allow the generated installer to allow for the user to install the application multiple times? I would imagine there would be changes needed for checking if the destination folder already has an installation there but what about removing the "already exist" detection or how to change the Add/Remove Programs to show nothing at all or each individual instance of the installation.
I have a web app and a web setup project in VS2010. By default, when I install my web app using my web setup project, in the Installation Address folder dialog window, the default Application Pool is DefaultAppPool. It has been stated in the MSDN documentation that we can change this default TARGETAPPPOOL, say to "ASP.NET V2.0". Here is the excerpt from MSDN... "The Application Pool list shows the available application pools on the target computer, and the default setting is named DefaultAppPool. To change the default application pool in your Web setup projects, you can use a post-build action to update the name of the application pool in the MSI." Is there anybody in the group knows the syntax on setting the TargetAppPool to another pool that exists in IIS, e.g., ASP.NET V4.0 CLASSIC?
I try to create a web setup project. Following this example ttp://weblogs.asp.net/scottgu/archive/2007/06/15/tip-trick-creating-packaged-asp-net-setup-programs-with-vs-2005.aspx everything was perfect. Now I need to find how going trought the wizard exclude some files from Content files Output.
Is it possible to debug a Web Setup Project, specifically its custom action code, by setting breakpoints and walking through the code? How does one do this?
In the Setup Project I have 2 web.config files: web.config - used during the development and web_dist.config - the one that should be included into Setup Project. I must be sure the the Setup project will NOT include the web.config and will always include web_dist.config.
In the File System -> Web Application Folder I have added the Content Files from the project. Also included the web_dist.config and mapped it to the web.config.
But this gives the warning:
WARNING: Two or more objects have the same target location ('[targetdir]web.config') And the actual config file included is web.config and not web_dist.config. What would be the best option to include the web_dist.config (and named as web.config in the setup)?
I have an installer class which I use to do some processing on the application after it is initially installed.
In the installer I have a custom dialog which requests a username and password. This is accessed in my installer class with Me.Context.Parameters("username")
After setting it as CustomActionData /username="[TXTUSERNAME]"
This is all fine. The first dialog of a Web Setup Project gets the user to select an IIS website from a dropdownlist and set a VirtualDirectory if required. I need to get the seleted Hostname but so far I have failed to find a reference to it in any documentation. I have tried things like:
I made Web Setp Project for a web application, I need to change virtual directory property for the web application.
This virtual directory is linked to TARGETVDIR property which is disabled in the property grid.But I need to control it, I searched for this and I found that the only way is to use orca.exe and change msi using it.
Can I amke another solution to avoid making modification on nsi after build???
Now i want to deploy that application without any interaction of IIS. I want to make setup of my project so that i can directly install it in client's pc. I have tried many ways of doing this. I have tried Xcopy method and even tried of adding web setup project.
I am using VS2010. When I am building a release for a WinForms Applicaiton, I can see some .xml files relevant to project in the bin elease folder. The .dll (third party component) has been referenced in the References folder of the project for eg. Rebex.Net.Ftp and in the properties window the Source Path is
C:Program FilesRebexFile Transfer Pack for .NET 4.0FTP SSL for .NET 4.0inRebex.Net.Ftp.dll In the above mentioned source path directory there is an Rebex.Net.Ftp.xml which gets pulled across to the release folder as well. I couldn't really get my head around where this can be referenced so that it puts this .xml file in the release folder of the project when I do a build?
My main problem is, when I created a setup project for this application, I can't get this file included in the installation pack (after installing the .msi file). I get the Rebex.Net.Ftp.dll but not Rebex.Net.Ftp.xml file. I tried all the options in the Project Output except including the "Source files" which I dont want to. how to include the .xml files in the setup installation pack, ie., if there are properties I am forgetting to set or something like that?
I want to know if there is a way to set up the default document or default web page from the setup project of a web page.What I mean is that I would like my web app installer to set the default page (i.e: DefaultPage.aspx) when installing the web application. I remember I could do this in previous versions of the asp.net platform, currently I am working in ASP.NET 3.5 (Visual Studio 2008).
I've just started investigating the Microsoft Ajax Minifer 4.0 for use with a Visual Studio 2008 Web Application I work on. It's proven easy enough to hook it into the .csproj file so it produced .min.js files for all scripts, however I'm stumped as to how to integrate this with the Web Setup project & Source Control.
Essentially what I want to do is have the resultant .min.js files included in the Web Setup project without having them included in Source Control because:
Having to check them out prior to the build being executing is a pain (the minifier cannot modify them if they're not checked out).
As they're created as a "build artifact" it just seems wrong to have them stored under source control.
The only option I've managed to come across so far is to explicitly include the .min.js files as part of the Setup project by right clicking on the Web Setup project and choosing "Add > File", and then having the relevant folder hierarchy duplicated in "File System on Target Machine" so that I can force the file to the correct location. This is neither elegant or simple/robust as:
It requires me to manually add every minified js file to the Web Setup project by hand Maintain a copy of the relevant directory structure in both the Web Application project and the Web Setup projec Remember to add any new js files minified versions to the Web Setup project.
Can I change algorithm of serial key template of web set up project ? If I am not able to change algorithm, what could be the best method to implement product key(serial number) concept in web setup project.
I created a web setup project. When the users install it, the virtual directory gets created and all the files are created under "C:Inetpubwwwroot<myvirtualdirectory>".
How to customize the web setup project so that I can change the virtual directory physical path? I had followed the tutorial
[URL]
but it didn't work and my MSI stopped installing alltogether.