1

Topic: InprocServer (DLL). I want DllInitialize, DllShutdown.

Here here one thought visited - it is a pity that the manager InprocServer (DLL with COM objects) does not support explicit initialization and  loaded DLL. It is possible to fulfill, of course, initialization/deinitsializatsiju in DllMain. But in DllMain it is impossible to launch and stop flows. And if there were explicit functions (DllInitialize, DllShutdown) problems with flows would not be. Strange that for the past of 20 years in Microsoft such idea not appeared. Like in Windows 8 they COM well enough shook up, and this thing did not invent

2

Re: InprocServer (DLL). I want DllInitialize, DllShutdown.

> it is strange that for the past of 20 years in Microsoft such idea not appeared. > Like in Windows 8 they COM well enough shook up, and this thing did not invent So do global  , considering  all objects created inside , and the turns out DllShutdown at achievement of its zero

3

Re: InprocServer (DLL). I want DllInitialize, DllShutdown.

Hello, ononim, you wrote: >> it is strange that for the past of 20 years in Microsoft such idea not appeared. >> Like in Windows 8 they COM well enough shook up, and this thing did not invent O> So do global  , considering  all objects created inside , and the turns out DllShutdown at achievement of its zero At me and is made right now. I want that flows continued to exist (in a pool) after clearing of the last COM object.

4

Re: InprocServer (DLL). I want DllInitialize, DllShutdown.

Hello, Kovalenko Dmitry, you wrote: O>> So do global  , considering  all objects created inside , and the turns out DllShutdown at achievement of its zero > At me and is made right now. > I want that flows continued to exist (in a pool) after clearing of the last COM object. Imho flow life can be prolonged to call DllCanUnloadNow. If DllCanUnloadNow returns S_OK it is necessary to prepare for outswapping and to stop background operations, and if S_FALSE we continue to do the useful background operation.