NET Installation and Configuration Issues Quick Navigation Visual C++ Programming Top GetWindowText and other Windows stuff is loaded from user32.dll. Conversely, calling functions such as these during termination can cause access violation errors because the corresponding component may already have been unloaded or uninitialized. For example, calling User, Shell, and COM functions can cause access violation errors, because some functions load other system components. For example, DllMain can create synchronization objects such as critical sections and mutexes, and use TLS.Ĭalling functions that require DLLs other than Kernel32.dll may result in problems that are difficult to diagnose. Therefore, the entry-point function can call functions in Kernel32.dll that do not load other DLLs. Similarly, the entry-point function must not call the FreeLibrary function (or a function that calls FreeLibrary) during process termination, because this can result in a DLL being used after the system has executed its termination code.īecause Kernel32.dll is guaranteed to be loaded in the process address space when the entry-point function is called, calling functions in Kernel32.dll does not result in the DLL being used before its initialization code has been executed. This can result in a DLL being used before the system has executed its initialization code.
It must not call the LoadLibrary or LoadLibraryEx function (or a function that calls these functions), because this may create dependency loops in the DLL load order. The entry-point function should perform only simple initialization or termination tasks. Possible reason, from DllMain MSDN topic:
0 kommentar(er)
