IIS does not control appdomain, this is done by the asp.net isapi filter.
asp.net run a file monitor looking for changes to files. if any changes are
seen, on the next request, a new appdomain is spun up (to load the new code
in), and all new requests go to it. the old app domain finishes the request
its processing and exits (hopefully). spinning up the new appdomain fires
Application start/etc and a new Application state.
while its technically possible to copy the application state objects to the
new domain, they would all have to be serializable (to marshal across domain
boundries), which currently is not a requirement for application objects.
what is guanenteeded is that the application start routine will be called
before any request.
-- bruce (sqlwork.com)
<ne************@hotmail.com> wrote in message
news:11**********************@u72g2000cwu.googlegr oups.com...
I have heard that IIS may decide to spawn one or more additional app
domains for a single ASP dot net application.
Is this true?
Is there a difference in how this works in IIS 5 and IIS 6?
Is it configurable?
Finally, if a new app domain is spawned for a single application, does
this equate to a totally different application (with its own
Application state, and its own Application_Start/Application_End
events, etc.)?
Thanks,
Jonathan