LoaderLock was detected when running VLIDE while debugging a .NET AddIn

By Adam Nagy

I get a "LoderLock was detected" with the below information when I run command VLIDE while debugging my .NET AddIn: "Attempting managed execution inside OS Loader lock. Do not attempt to run managed code inside a DllMain or image initialization function since doing so can cause the application to hang." What could I do?

Solution

You can simply disable the Loader Lock detection in this case in Visual Studio:

Go to Debug > Exceptions… > Managed Debugging Assistants > LoaderLock and untick it.