G
Guest
I have what I think should be a pretty common scenario in a corporate
environment. I have a web app and three environments on three servers:
Development, QA and Production.
We develop in development and then deploy the updated application to our QA
server and then once tested to our production server.
The application has a web.config file. The contents of the file
(appsettings part) are different in all three environments because each
enviroment connects to different databases (a dev, qa and the prod database).
what I'm discovering is that the Publish option in VS2005 won't work in this
scenario because it will copy web.config from development to QA or production
and thus result in the incorrect appsettings...i.e. Production all of a
sudden connecting to the development database.
Is there any way around this with the Publish command? Or do i have to
manually use "Copy Web" which is more timeconsuming?
Excluding web.config does't work because the web.config in the destination
is still wiped out. I tried setting web.config to Read ONly in QA and
production but it is still deleted and overwritten by the one from dev.
Seems like someone really didn't think of this common scenario. An "Exclude
web.config" checkbox would have been all that was necessary. Or is this
hidden somewhere?
Thx.
R-
environment. I have a web app and three environments on three servers:
Development, QA and Production.
We develop in development and then deploy the updated application to our QA
server and then once tested to our production server.
The application has a web.config file. The contents of the file
(appsettings part) are different in all three environments because each
enviroment connects to different databases (a dev, qa and the prod database).
what I'm discovering is that the Publish option in VS2005 won't work in this
scenario because it will copy web.config from development to QA or production
and thus result in the incorrect appsettings...i.e. Production all of a
sudden connecting to the development database.
Is there any way around this with the Publish command? Or do i have to
manually use "Copy Web" which is more timeconsuming?
Excluding web.config does't work because the web.config in the destination
is still wiped out. I tried setting web.config to Read ONly in QA and
production but it is still deleted and overwritten by the one from dev.
Seems like someone really didn't think of this common scenario. An "Exclude
web.config" checkbox would have been all that was necessary. Or is this
hidden somewhere?
Thx.
R-