Attempting to execute managed code within the OS loader lock. Do not try to run managed code in the DllMain or image initialization function, osdllmain

Attempting to execute managed code within the OS loader lock. Do not try to run managed code in the DllMain or image initialization function, osdllmain

 

From: http://www.cnblogs.com/lcxu2/archive/2011/01/16/2004016.html

Attempting to execute managed code within the OS loader lock. Do not try to run managed code in the DllMain or image initialization function... (16:17:14) Reprinted

Tags: it

Category: C #

When I call an external dill during form initialization, it will throw a "attempt to execute managed code within the OS loader lock" for unknown reasons. Do not try to run the managed code in the DllMain or image initialization function. "The program is stuck and checked online. The related instructions are as follows :. in NET2.0, 42 powerful debugging assistants are added. loaderlock is one of them. Loaderlock detects the running of hosted code on a thread with the operating system loader lock. This may cause deadlocks and may be used before the operating system loader initializes the DLL. Generally, this means that the form is not completely generated, and you call other dll at this time, and this exception may be thrown! To solve this exception, debug the vs2005 menu and choose "exception"> "Managed Debuggin Assistants"> "LoaderLock" to remove the selected status. If no exception exists, on the tool --- custom --- command tab --- Select Debug on the left -- press Ctrl + Alt + E on the right side of the exception menu, modify the selected status of Managed Debuggin Assistants-> LoaderLock. Remove Method 2 from HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \. add a String under NETFramework with a value of "0". However, in this case, all. NET2.0 development does not get the benefits of MDA.
Trying to execute managed code in the OS loader lock. Do not try to run managed code in the DllMain or image initialization function.

Press Ctrl + Alt + E to modify the selected status of Managed Debuggin Assistants-> LoaderLock.
 
C # How to Solve exceptions

Your managed code is written in the initial function.
This write is invalid.
Just change the location. Do not call managed functions during form initialization.