View Complete Post
I am using VS2005.
I don't have much experience with web setup projects, but I now need to create a decent windows installer in order to allow customers to install one of our web applications. I have created a simple web setup project and it works fine, but not when it comes to upgrades of the application.
If for instance I install version 1.0 on a machine, and then later I try to install version 2.0, I don't seem to have the control that I would like... I can specify in the web setup project that the installer must enforce an uninstall of previous version, but then all application files and logs are uninstalled as well. If I let the application just install itself over the older version, it seems to leave some old DLL's there - it then causes issues in the application because DLL version conflicts.
My basic requirement is that I would like th installer to upgrade the old version with all the files required, but leave any application and log files in tact - this way the customer won't have to reconfigure the application after install.
What is the best way to handle this?
I have a sample Web Application Project and using Web Deployment Project i'm generating the precompiled version of that.
Now i want to create a WebSetup project in my solution using the Output generated by the WebDeployment project.
Please let me know how to achieve this.
Visual Studio 2005 introduces a new model that lets you define your own project templates and starter kits, something developers have been requesting for some time. Here Matt Milner shows you how to consume, create, and customize these templates.
MSDN Magazine January 2006
I am not sure if here is a proper place to ask this question. I look for other forums, and don't feel this question can fit in any. If this is not a correct place to post, I appologize. Please let me know where I can get answer for this question. Thanks.
Here is my question.
I wrote a website, and not I am trying package it with a setup program (msi), so I created a "Web Setup Project" and specify outputs as the standard tutorial on this. And then I'd add custom action to msi which modify Web.config file during msi installation. Output looks ok, but msi install the website under "C:\Inetpub\wwwroot" folder, and I don't have control on it. I followed an example (http://www.codeproject.com/KB/install/ChangeVDirWebSetupProject.aspx) use orca.exe to remove WEBCA_EvaluateURLsMB, WEBCA_EvaluateURLs and WEBCA_EvaluateURLsNoFail from corresponding tables in msi and provides TARGETDIR value while calling the msi file. And then I fall in a problem, either the custom action is not called any more or I get a error "Configuration file cannot be created".