I am on an application team that currently has 7 environments other than the production environment. We have 4 config files that we always have to change any tiem we install in a different environment. I am curious the best way to go about this...
Ideally we would like to NOT have to do a build for each environment which is what it seems this link discusses:
http://weblogs.asp.net/scottgu/archive/2007/09/21/tip-trick-automating-dev-qa-staging-and-production-web-config-settings-with-vs-2005.aspx
I thought about something more along this line, but not sure that is the best bet either...
http://blog.andreloker.de/post/2008/06/Keep-your-config-clean-with-external-config-files.aspx
Maybe you should always build for each environment? Not sure if there is a way to do one build and then based on the environment the correct file loads? Maybe by the server name it is on?
Any help or direction would be appreciated. Right now we have a file for each of our 3 services and the web.config and when we install we go in and comment/uncomment sections...
thanks,
rgn
ASKER