Monday October 12th

Friday October 9th

Deploying config files to multiple environments - dev, stage, prod

A common problem most application developers face at one time or another is managing the deployment of the environment specific configuration elements their application depends on. Most often these elements include items like connection strings, file paths or other settings the application requires access to during runtime. I recently tackled this problem and came up with a solution that seems to work pretty well (we have been using it for the past 4 months without any issues) and fits in great with our automated build enviornment.


Commenting on Stories is limited for now and will open up to those recommended by the community. Learn how
Loading DotNetKicks...
brought to you by the Kicks Network