We have an answer to this from a MSFT authorized source.
---000---
One way to handle it is to use configuration file fragments and point
to them in your web config file. Your fragment would look like this,
without the namespace:
<connectionStri ngs>
<clear />
<add name="Northwind SQL"
connectionStrin g="Data Source=(local); Initial
Catalog=Northwi nd;Integrated Security=true;"
providerName="S ystem.Data.SqlC lient" />
</connectionStrin gs>
Your Web config would have this line, which uses the fragment:
<connectionStri ngs configSource="c onnections.conf ig"/>
One significant advantage of using config file fragments for ASP.NET
apps is that config file fragments can be edited at runtime without
causing an application restart.
---000---
You can modify that example for different configuration sections.
Juan T. Llibre
ASP.NET MVP
============
"Ashish" <as*****@thisis junk.com> wrote in message news:O0******** ******@TK2MSFTN GP14.phx.gbl...
Iam using a couple of external (other than web.config) configuration files for my project , and i
want their behavior to be like that of web.config file ( the application should track changes and
reload if required),
is this possible in the new ASP.Net 2.0 ?
thanks