Build Deployment vs. Production app.config?

[Spam Catcher]

Is there a way to script VS.NET to copy different app.config along with
different build configurations?

In fact, it would be great if I could dynamically substitute app.config
values for different deployment scenarios.

Any tips or tools to do this?

Thanks!

[Parag Joshi]

HI
We did this by creating different app.config's for each environment
(Dev,QA,UAT, PROD) etc. Then we build an installation package (msi) which
can be done from within visual studio itself. Its a project type.

In the installation you can can create a selection environment variable and
then depending on the user or command line input copy the appropriate
app.config.QA or app.config.UAT as Application.exe .config file.

Other than this i am not aware of any built in support. An alternative way
of doing this is to specify an override file. However the same scenarios
would apply as you would need a different override file depending on the
environment.

Hope this helps
Regards
Parag

"Spam Catcher" <sp**********@r ogers.comwrote in message
news:Xn******** *************** ***********@127 .0.0.1...

Is there a way to script VS.NET to copy different app.config along with
different build configurations?

In fact, it would be great if I could dynamically substitute app.config
values for different deployment scenarios.

Any tips or tools to do this?

Thanks!

[Spam Catcher]

"Parag Joshi" <pa***@nospam.n ospamwrote in
news:#E******** ******@TK2MSFTN GP02.phx.gbl:

We did this by creating different app.config's for each environment
(Dev,QA,UAT, PROD) etc. Then we build an installation package (msi)
which can be done from within visual studio itself. Its a project
type.

In the installation you can can create a selection environment
variable and then depending on the user or command line input copy the
appropriate app.config.QA or app.config.UAT as Application.exe .config
file.

Other than this i am not aware of any built in support. An alternative
way of doing this is to specify an override file. However the same
scenarios would apply as you would need a different override file
depending on the environment.

Thanks for your help - sounds like a good alternative method.

It's too bad VS.NET doesn't have something built in for this type of stuff
.... considering it already handles different build configurations. .. would
be natural to handle different .config files too.

I'll give your method a try!