managing web.config in different environments...
- From: "sqlster" <trisha@xxxxxxxxxxxxx>
- Date: Thu, 8 Sep 2005 16:15:02 -0700
We have 3 different environments: dev, qa, and production. After unit
testing, the application is deployed to dev for unit testing among the
programmers and business analyst. When that is okay it gets deployed to QA
for other qa teams to test. When that is approved, it gets deployed to
production.
For each environment we have web.config in VSS such as dev.web.config,
qa.web.config and so on. The developer that adds an app setting key into
dev.web.conifg also makes sure that this key makes into all the web.configs
including the production one in VSS. Any time the application gets rolled out
to lets say qa, we use qa.web.config with its respective settings.
Now netops team that does the production deployment are recommending another
plan. They want to have a central configuration file for all the settings for
all the web applications in the enterprise in one central location. Each
application will be provided a guid and based on that guid, via web service,
client application, will extract its settings along with connection string.
Does that idea from netops make sense??
How do you guys out there manage your web.configs for different environments??
.
- Follow-Ups:
- Re: managing web.config in different environments...
- From: Brock Allen
- Re: managing web.config in different environments...
- Prev by Date: Re: C# newbie
- Next by Date: Re: Absolute Beginner
- Previous by thread: Loop Through / Delete From ListBox
- Next by thread: Re: managing web.config in different environments...
- Index(es):
Relevant Pages
|
