Message from discussion VS 2005 LoaderLock problem

From: "Glass Half Full" <sta...@nospam.nospam>
References: <OcprpL2#FHA.228@TK2MSFTNGP12.phx.gbl> <FaC4sf7#FHA.552@TK2MSFTNGXA02.phx.gbl>
Subject: Re: VS 2005 LoaderLock problem
Date: Thu, 8 Dec 2005 16:49:15 -0500
Lines: 30
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
Message-ID: <eG5r9EE$FHA.208@tk2msftngp13.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!newsfeed.stanford.edu!headwall.stanford.edu!newsfeed.news2me.com!newshub.sdsu.edu!msrtrans!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl

One more data point on the debug problem.

It was determined that if (in Project/Properties/Debug) "Enable unmanaged 
code debugging" is set (box checked), the MDA problem goes away.  At this 
point I have no idea why this would effect the problem, but it does.


""Peter Huang" [MSFT]" <v-phu...@online.microsoft.com> wrote in message 
news:FaC4sf7%23FHA.552@TK2MSFTNGXA02.phx.gbl...
> Hi
>
> It seems to be the new feature in Whidbey which is called Managed 
> Debugging
> Assistants.
> http://msdn2.microsoft.com/en-us/library/d21c150d.aspx
>
> If you did not want that you may try to follow the steps above in disable
> the feature.
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
>