Winform problem highlights, winform

Winform problem highlights, winform
Attempting to execute managed code within the OS loader lock. Do not try to run managed code in the DllMain or image initialization Function

Description

In. NET2.0, 42 powerful debugging assistants are added, and MDA. 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.

Method 1 (pass test)

Generally, this means that the form is not completely generated, and you call other dll at this time, and this exception may be thrown!
Press Ctrl + Alt + E or debug-> 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-side Navigation Pane, drag the exception to the menu, and modify the selected status of Managed Debuggin Assistants-> LoaderLock.

Method 2: In HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \. add a String under NETFramework with a value of "0". However, in this case, all. neither NET2.0 nor NET2.0 has the advantage of Mobile Desktop Assistant (MDA.