Single Installer for multiple environments

With quite a few contracts I have been working on over the years I have ended up helping out with the build process for ASP.Net websites. Many existing enterprise build processes I have encountered tend to involve making a custom build of the codebase for UAT and then once UAT is passed making another build for PROD. This process brings in a significant risk of a developer on a team checking in changes AFTER UAT was build and thus ending up with untested code in PROD.
This risk is unnecessary. The following is an approach I have used at a number of enterprises for creating a single .msi installer which can be run in a DEV environment (if it exists), then copied into a UAT environment for user testing before finally being copied and run in PROD. The single installer gets built once but can handle the different server/database configurations of the different environments and can install the correct .config files in each environment.
The methodology is as follows:
  1. Within Visual Studio, add a Setup Project to the solution
  2. Create different copies of the Web.config for each target environment. Each web.config (e.g. web.config.UAT) can then be tailored to each environment. You should end up with a project similar to the following:

  3. Change the Properties of the original web.config and set its "Build Action" to "None" 
  4. Right-click on the Installer project and View -> File System
  5. In the Application Folder, add the new web.config files (DEV, UAT and PROD). You should end up with the following: 
  6. For each of our three files set the following properties:   

Transitive: True
Vital: False
Condition: ENVIRONMENTNAME="DEV"
   ->Replace "DEV" with "UAT" and "PROD" for the other configs 
TargetName: web.config

    For example with the UAT file: 
   
Then, when installing at each environment, use similar to the following at the command line:
msiexec /q /i "Installer.msi" ENVIRONMENTNAME="PROD"

The ENVIRONEMNTNAME flag which is passed into msiexec tells the installer to use the file(s) marked with the same Condition property (step 6 above). Thus, the right config file gets chosen for each environment. I have used this approach successfully many times with Visual Studio 2003, 2005 and 2008.
Hope its of help!

Popular posts from this blog

Splitting a polygon using SQL Server Spatial queries

Image
A recent project involved drawing regions on a map of a country using the Bing Maps Silverlight control . The user could zoom in to a suburb and draw a region (polygon) around an area on the map. Another feature, and hence the purpose of this blog post, involved enabling a user to draw a line through a region (polygon) and split the region in two: how was that splitting done? Note: you will probably need some database experience and ideally some Bing/Google Maps experience for this to make sense A quick intro to SQL Server Spatial queries SQL Server 2008 introduced support for geo-spatial data . The two new spatial data types are: Geometry: supports flat data surfaces. The following will create a polygon and a line and you can see that our resulting rectangle and line are straight: DECLARE @Geometry GEOMETRY = 'POLYGON((10 10, 40 10, 40 40, 10 40, 10 10))' DECLARE @Linestring GEOMETRY = 'LINESTRING(5 5, 50 50)' SELECT @Geometry SELECT @Linestr
Read more

Setting up SourceTree, BitBucket, SSH with a proxy on Windows

Image
When using SourceTree to connect to Bitbucket with an SSH key through a proxy server, there are a number of steps to follow... SourceTree setup 1. Open SourceTree, goto Tools and select 'Create or Import SSH Keys' 2. A dialog will open up. Click Generate to generate a public private key pair:   Provide a suitable passphrase and save both the public and private keys 3. In your system tray, right click on Pageant (PuTTY authentication agent) and select "Add Key"   Select the private key you created in step 2 Proxy Setup with Putty 1. Setup your HTTP Proxy settings in Putty Click on your Start button and search for Putty When Putty comes up goto the Session Category 'Default Settings' and then Load Goto the Proxy category and add in the proxy settings, making sure to select the right proxy type Go back to the Session Category and save the updates to the Default Settings   Bitbucket setup 1. Goto BitBucket, navigate to "Your Acc
Read more

MVC HTTP Headers for CDN caching

Image
On a recent project I added upgraded our systems to use a Content Delivery Network (CDN). The project supplied content to users and we wanted to offload the 'heavy-lifting' of the content supply away from our PROD server onto a more robust delivery network. The mobile clients would request the content from the CDN. If the CDN hadn't cached the content yet, it would grab it from our PROD server, cache it, and respond back to the clients. For this caching to work, though, some HTTP Header magic was required. Which headers should you watch out for? Cache control should be public For the CDN to cache the content on behalf of your origin server, set the Cache-control=public Expires Date To stop the CDN regularly requested the same static content from your PROD server, set the Expires-Date setting to be in the far future (e.g. > 1 year)  Vary  Watch out for the 'Vary' header. MVC3 had initially defaulted to adding the "vary=*" http head
Read more