Disclaimer: The way this works and is setup in code has it's advantages but I wouldn't describe it as 'graceful'. It's a bit hardcoded but It works well enough though. Ideally adding and removing environments and their details should be a matter of adding a row to an XML file...just haven't had time to change it over.

How Its All Linked Together

There are a few peices that are linked together:-
1. The build.environment file (BuildEnvironment).
2. The dataConfiguration block in the app.config (Enterprise Library Data Application Block)
3. The classes in Agile.Common.csproj in the 'Environments' directory.

In the App.Config you will have

Create a new Environment

1. Create a new class in Agile.Common.Environments.
2. Inherit from AgileEnvironment
3. Override all of the abstract properties.

Current Valid Environments

  1. Build
  2. Development
  3. UAT
  4. Production
  5. HotFix
  6. HotFixUAT
  7. Training

Note that some of the code doesn't relate to the updater, that's because the code is reused by another application that automates promotion to the different environments.

Last edited May 18, 2008 at 11:27 AM by wallism, version 2


No comments yet.