deploying app

[neilmcguigan]

my local web.config on my development machine is different than the
live version, ex some hardcoded paths (required by a stupid control)
and debug=true vs false

what's a good way to keep live and test web.configs synchronized, ie if
i add a setting, but maintain the necessary differences?

TIA

neil

 

[Guest]

Have a look at the appSettings element's "file=" attribute:

http://msdn2.microsoft.com/en-us/library/ms228154(VS.80).aspx

Peter

 

[Craig Deelsnyder]

my local web.config on my development machine is different than the
live version, ex some hardcoded paths (required by a stupid control)
and debug=true vs false

what's a good way to keep live and test web.configs synchronized, ie if
i add a setting, but maintain the necessary differences?

TIA

neil

You can store settings outside of an individual web.config file. For
appSettings you can specify an external file with 'common' settings:

<appSettings file="user.config">
....
</appSettings>

appSettings has another attribute, configSource, that I'm not as familiar
with. <connectionStrings> node also has a configSource attribute to
specify the name of the file with the configuration section in it. I
believe this latter attribute you can't define any of the node's settings
in the web.config, only in the 'included file'?? Not sure, but most root
nodes under <system.web> have this attribute as well....

http://weblogs.asp.net/pwilson/archive/2003/04/09/5261.aspx
http://www.codeproject.com/dotnet/appsettings_fileattribute.asp
http://msdn2.microsoft.com/en-us/li...n.sectioninformation.configsource(VS.80).aspx

 

[neilmcguigan]

Thank you very much!