I need to encapsulate a VB6 application as a COM object that will be called by IIS. One of the dlls used by the VB6 app is NOT thread-safe.
How can I make sure that whenever my COM object is called it doesn't share the same dll with other instances of itself?
I read somewhere that ActiveX exes run each instance in a different process, would that be enough?