Raheel,
This is not correct. A change to web.config causes the AppDomain of the
running application to be unloaded and a new AppDomain to be loaded with
ASP.Net runtime in it. Note that it's the AppDomain that the runtime is
hosted in (one for each virtual directory) that gets restarted not the
process.
The old AppDomain finishes running out requests while a new one is started
up to capture all new incoming requests so there may be two simultaneous
instances of the same application running for a short period of time.
+++ Rick ---
--
Rick Strahl
West Wind Technologies
http://www.west-wind.com/ http://www.west-wind.com/weblog/
----------------------------------
Making waves on the Web
"Raheel Hussain" <ra*******@yahoo.com> wrote in message
news:u$**************@tk2msftngp13.phx.gbl...
if you do any change to the web.config then the corresponding
application will immediately load the web.config file, but do not
restart.
the asp.net framework cashes all the settings of this file and
automatically detects and loads the settings when some modifications are
made to it, hense again takes them to the cache.
regads
raheel
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!