Quote:Option 1. Create web application installation package Use Web Setup Project for creating a web application installation package (.msi) Creating or Adding a Setup Project at MSDN You can create your installation the way it will offer user an Upgrate option of your application if it's already installed on his or her machine. That's not a problem. Alternatives to Web Setup Project (all of them can handle upgrade scenarios): Wise Installation StudioInstallShieldNullsoft Scriptable Install System - this one is free and open source Optoin 2. Deploy web application on the server You can use NAnt or MSBuild or IIS Web Deployment Tool for these tasks automation. For example with NAnt of MSBuild you could specify tasks like these: get project files from source repositoryupdate .config file and maybe some other files if neededcompile you web applicationupdate registry settings on the serverupdate database schema on the serversynchronize files (x-copy) between you build folder to IIS web folder Web Deployment Blog Option 3. Distribute your web applications via Web Plafrom Installer. http://www.microsoft.com/web/
Use Web Setup Project for creating a web application installation package (.msi)
Creating or Adding a Setup Project at MSDN
You can create your installation the way it will offer user an Upgrate option of your application if it's already installed on his or her machine. That's not a problem.
Alternatives to Web Setup Project (all of them can handle upgrade scenarios):
You can use NAnt or MSBuild or IIS Web Deployment Tool for these tasks automation.
For example with NAnt of MSBuild you could specify tasks like these:
Web Deployment Blog
http://www.microsoft.com/web/
var
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
Submit an article or tip