A common task in a project is preparing for a deployment. The easiest way to do this is making use of a Web Setup Project. But how do we make this Web Setup Project suitable for multiple environments, because it's most likely that there are environments like Development, Test, Acceptance and Production.
The key to this solution is the "Condition" property. If you add a file to the Web Setup Project (In the File System view right mouse button on the Web Application Folder, then Add -> File) and select it, you can find the "Condition" property in the properties window.
We add the following value to the "Condition" property ENV="Prod", this is for the production environment, for the test environment it will be something like this ENV="Test".
We also set the "TargetName" property to Web.Config so the Web Setup Project will output the configuration file as Web.Config.
Well you can add unlimited Web.Config files to your Web Setup Project, they are all output as Web.Config but not all at the same time. So how can we choose the correct Web.Config for your environment, well like this:
%windir%\system32\msiexec.exe /i "Setup.msi" ENV="Prod"
- msiexec.exe (the Windows installer)
- /i (is the install switch)
- "Setup.msi" (compiled output of the Web Setup Project)
- ENV="Prod" (the condition value)
If you run this, the setup will be started. After the setup is finished, you will notice that only the Web.Config is installed with the "Condition" property set to ENV="Prod".
To make this all fool proof, you can make a shortcut to this command line, like this:
Now when you click on this shortcut, you get the same result.
So with this solution, you can make one Web Setup Project for all your environments and create a better and stable deployment solution.
- 26th January, 2009: Initial post