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

Message from discussion VS 2005 LoaderLock problem
From: "Glass Half Full" <sta...@nospam.nospam>
Subject: VS 2005 LoaderLock problem
Date: Wed, 7 Dec 2005 14:17:47 -0500
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <OcprpL2#FHA.228@TK2MSFTNGP12.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework
NNTP-Posting-Host: sas12014.nat.sas.com 149.173.12.14
Path: g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl

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