Hi David,
Any update to the web.config file will cause the current ASP.NET process,
which is serving the aspx page that made a change to the web.config file,
to be recycled and a new ASP.NET process will be created to continue
serving any subsequent request.
In this case, recycling and re-creating of the ASP.NET process will cause a
lot of issues, such as any pre-stored object will be lost, the original
session will be destoried, and so forth.
I suggest that we do not store the frequently-changed connectionstring in
the web.config file. Instead, we can put the into another file.
Best regards,
Jacob Yang
Microsoft Online Partner Support
<MCSD>
Get Secure! ¨C
www.microsoft.com/security
This posting is provided ˇ°as isˇ± with no warranties and confers no rights.