Ensures that the specified DLL remains loaded as long as there are outstanding callbacks.
- pcbe [in, out]
A TP_CALLBACK_ENVIRON structure that defines the callback environment. The InitializeThreadpoolEnvironment function returns this structure.
- mod [in]
A handle to the DLL.
This function does not return a value.
You should call this function if a callback might acquire the loader lock. This prevents a deadlock from occurring when one thread in DllMain is waiting for the callback to end, and another thread that is executing the callback attempts to acquire the loader lock.
If the DLL containing the callback might be unloaded, the cleanup code in DllMain must cancel outstanding callbacks before releasing the object.
Managing callbacks created with a TP_CALLBACK_ENVIRON that specifies a callback library is somewhat processing-intensive. You should consider other options for ensuring that the library is not unloaded while callbacks are executing, or to guarantee that callbacks which may be executing do not acquire the loader lock.
The thread pool assumes ownership of the library reference supplied to this function. The caller should not call FreeLibrary on a module handle after passing it to this function.
This function is implemented as an inline function.
To compile an application that uses this function, define _WIN32_WINNT as 0x0600 or higher.
Minimum supported client
|Windows Vista [desktop apps only]|
Minimum supported server
|Windows Server 2008 [desktop apps only]|
- Thread Pools
Build date: 11/21/2012