Luis, I'm not aware of a way to automate configuration differences in
Web.config across DEV / TEST / PROD. In our environment we manage this as
follows;
+ All web projects have a /deploy/test and /deploy/prod subdirectory,
containing any files that supercede the DEV versions. Web.config is the
most common entry here, but on occasion certain XML files, etc may change
during deployment.
+ We maintain the DEV, TEST, and PROD versions of these files separately.
DEV files being in the normal location within the source. All files are
managed in source control.
+ At deployment, we run a custom tool that deploys the files from (e.g.)
DEV to TEST, and then overlays the files from the /deploy/test directory.
This ensures that anything different between DEV and TEST, or between TEST
and PROD, can be handled automatically at deployment.
If you cannot find a better option, you might consider going this route.
There are other advantages to the custom-deployment-tool approach as well,
like being able to send email notifications to the TEST team, logging
deployment events in a database, updating change histories from source
control, avoiding the copy of undesired files (*.cs, *.scc, etc) and
directories (/deploy/*, /debug/*, etc), temporarily displaying a "The site
is being updated" message, and so on.
"Luis Esteban Valencia" <lu*******@hace b.com> wrote in message
news:#5******** ******@TK2MSFTN GP12.phx.gbl...
Hi,
I want in debug mode debug=true. In release (production), no reason debug
to be true but the questions are:
1. Does it slow the application (holding debug=true)
2. If yes, how can I solve the problem so that in debug mode debug=true
and in realse debug=true. To hold 2 separate files - seems not so good idea
Additional question: is there any correlation between debug in web.config
file and Project settings?
thanks
--
LUIS ESTEBAN VALENCIA
MICROSOFT DCE 3.
MIEMBRO ACTIVO DE ALIANZADEV
http://spaces.msn.com/members/extremed/
