ASP.NET 2.0 environment.
I have to change connection strings in all of our websites' web.config files... and it's a lot of files!
I was hoping to be able to use an external config file for this, and place it somewhere where all apps could read it, but it turns out that something like:
or
is not permissible, as the configSource attribute must be a relative physical path.
In theory I suppose one could store connection strings in the machine.config - however that not only feels wrong, but also as far as I can tell would require codebehind changes, which is not an option at this stage
Has anyone had a similar situation? Or got any suggestions?
I would appreciate any advice
Thanks
~LFCfan
I have to change connection strings in all of our websites' web.config files... and it's a lot of files!
I was hoping to be able to use an external config file for this, and place it somewhere where all apps could read it, but it turns out that something like:
Code:
<connectionStrings configSource="./ConfigFileSections/ConnectionStringsMaster.config"/>
Code:
<connectionStrings configSource="c:\ConfigFileSections\ConnectionStringsMaster.config"/>
is not permissible, as the configSource attribute must be a relative physical path.
In theory I suppose one could store connection strings in the machine.config - however that not only feels wrong, but also as far as I can tell would require codebehind changes, which is not an option at this stage
Has anyone had a similar situation? Or got any suggestions?
I would appreciate any advice
Thanks
~LFCfan