> My first question would be for what purpose? My application caches data in a singleton. Eventually this data goes out of date. I need a second AppDomain in order to cache fresh data in the singleton. Note that I do *NOT* want to update the first AppDomains's cache. I just want it to die a normal death as the sessions using it expire.
> Changing the Web Config file for an ASP.NET application will cause a > second Instance in a new App Domain to be created and furthermore new > sessions are handled by the second instance. Yes, but I have found that all sessions for the first AppDomain are immediately invalidated when this happens. Is there any way to keep these sessions active? -- Brian
