#Everweb delay loading code#

The HMODULE for the loaded DLL, if it loaded the DLL itself. If the notification is dliNotePreLoadLibrary, the hook function can return:Д , if it just wants informational notifications. It lets you supply your own load handler. It's useful to call just for informational purposes.Д«ypass the default delay-load handling. The default helper handles the loading of the DLL. If the notification is dliStartProcessing, the hook function can return: GetProcAddress is called to attempt to get the address of the procedure.Д«y supplying a new definition of the pointer _pfnDliNotifyHook2 that's initialized to point to your own function that receives the notifications.Д«y setting the pointer _pfnDliNotifyHook2 to your hook function before any calls to the DLL that the program is delay loading. LoadLibrary is called to attempt the load of the DLL. The stored handle to the library is checked to see if it has already been loaded. The delay load notification hooks are called just before the following actions are taken in the helper routine: There are notification hooks and failure hooks. It could also throw its own exception or longjmp out of the hook.

Or, it can return 0 to indicate that an exception should be thrown. The hook routine needs to return a suitable value, so that processing can continue (an HINSTANCE or FARPROC). You can provide a hook to the helper function that can supply the alternative code, or remedy the situation.

#Everweb delay loading code#

Your code may need to recover on a failure, or to provide an alternate library or routine. Failure handling is composed of two portions: Recovery through a hook, and reporting via an exception.ДЇor more information on DLL delay load error handling and notification, see Understand the helper function.ДЇor more information on hook functions, see Structure and constant definitions. If your program uses delay-loaded DLLs, it must handle errors robustly, since failures that occur while the program is running will result in unhandled exceptions.