Since the following user seems to have the similar...

2009-02-17T15:31:00.000-05:00

Since the following user seems to have the similar issue, I copy/paste the whole email for reference.

Based on your description, my understanding on your problem is that you have an ASP.NET web application which uses a managed C++ component library that act as a wrapper of an unmanaged c++ dll. This application works well
when there is only single web application work in the Application Pool, but get messed state management when running multiple web applications in the same application pool(IIS), correct?

As you mentioned that the C++ unmanaged dll uses some static variables to manage global connection pool(or other states), I think this should be the cause of the problem. As for ASP.NET(or other .net framework/clr based
application), it is running at AppDomain based boundary, that means global variables(static class members in .net applications) is only visible in its own AppDomain, not in the entire host process(which is different from the variable sharing scope for win32 application---process based scope).

For your scenario, in IIS6, all the ASP.NET applications (which use the same App Pool) will be hosted in the same worker process, therefore, if you've used any unmanaged c++ code which use global variables, they'll be
accessible by all the applications in the worker process no matter they're in the same AppDomain or not. Therefore, I'm wondering whether it is possible that you'll configure those applications to use separate application pool(in IIS) if they'll access the same win32/c++ global variables? So far this is the only means I can get to prevent the win32/ c++ global variables to be accessed by multiple applications.

Comments on Bing Xia's Blog: Run Win32 application in its own application pool

Since the following user seems to have the similar...