~mkw

Not exactly what you want...but you can use a user.config file for appSettings e.g.:

appSettings file="user.config"

You then just use a user.config for each environment - that way your user.config can stay the same...

Include a Release.Web.config in your assembly as an embedded resource and stream it to disk using a .NET Installer Class when you install your software.

We created a wrapper around AppSetting and ConfigurationSettings that looked at various things (machine name, database server, ...) to determine the environment and use the correct settings. I.e.

<test-environment>
<add key="config-section-setting" value="test1" />
<add key="duplicate-setting" value="from test section" />
<add key="custom-section" value="machine-env-mapping" />
</test-environment>

<alternate-environment></alternate-environment>

<!-- Include the common machine to environment mappings -->
<machine-env-mapping>
<add key="test-machine" value="test-environment" />
<add key="alternate-machine" value="alternate-environment" />
</machine-env-mapping>

rttttttttty