Question

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?

Was it helpful?

Solution

Your going to need to read up on COM and apartment threading models, link text. While what your doing is possible your performance is going to be horrible because you will end up using single threaded apartments, so all requests will be serialized. You really should investigate creating a separate process for each of these requests.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top