> Move your Sessions out of process (either into the ASP.NET State service > or a SQL server) - see the sessionState element in the web.config.
My sessions are already out of process, but that's not relevant to the problem at hand. The data I'm concerned about is cached in memory and shared by all sessions. What I need is a way to start a separate instance of an ASP.NET application in a second AppDomain. Perhaps this is not possible? -- Brian
