VS 2005 LoaderLock problem - microsoft.public.dotnet.framework

Message from discussion VS 2005 LoaderLock problem

Glass Half Full

View profile

More options 7 Dec 2005, 19:17

Newsgroups: microsoft.public.dotnet.framework

From: "Glass Half Full" <sta...@nospam.nospam>

Date: Wed, 7 Dec 2005 14:17:47 -0500

Local: Wed 7 Dec 2005 19:17

Subject: VS 2005 LoaderLock problem

  Reply to author
  |
  Forward | Print | View thread
  | Show original
  | Report this message | Find messages by this author
  

I'm using VS 2005 (v8.0.50727.42 (RTM.050727-4200) with the v2.0.50727
framework.

I have a problem. I can instantiate a COM object, but the first time I try
to use the object I get the following exeception:

LoaderLock was detected
Message: 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.

If I disable this exeception the application does indeed hang. However, if
I run this application outside the debugger it runs fine. If I recompile on
a different machine, I can run it in the debugger.

What exactly is this error message suppose to be telling me? I'm not
running managed code inside DllMain or a image initialization function.

Is there any hope this can be fixed, or do I need to go back to vs2003 where
the debugger worked?

Thanks

Reply to author Forward