Running non-thread-safe dll on a Windows multi-threaded HTTP server

I need to encapsulate a VB6 application as a COM object that IIS will call. One of the libraries used by the VB6 application is not thread safe.

How can I make sure that whenever my COM object is called, it does not use the same DLL with other instances?

I read somewhere that ActiveX exes starts each instance in a different process, would that be enough?

+3
source share
1 answer

COM , . , , , . .

+1

Source: https://habr.com/ru/post/1704831/


All Articles