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

Message from discussion VS 2005 LoaderLock problem
From: "Kevin Spencer" <ke...@DIESPAMMERSDIEtakempis.com>
References:  <OcprpL2#FHA.228@TK2MSFTNGP12.phx.gbl> <FaC4sf7#FHA.552@TK2MSFTNGXA02.phx.gbl> <uHLnaNA$FHA.3464@TK2MSFTNGP15.phx.gbl> <2FF0F5A7-8AAD-4301-A706-8A039A564978@microsoft.com>
Subject: Re: VS 2005 LoaderLock problem
Date: Mon, 30 Jan 2006 13:50:34 -0500
Lines: 115
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Original
Message-ID: <#KUxO4cJGHA.2300@TK2MSFTNGP15.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework
NNTP-Posting-Host: 65-113-65-130.dia.cust.qwest.net 65.113.65.130
Path: g2news1.google.com!news1.google.com!news3.google.com!news.glorb.com!newsfeed.cw.net!cw.net!news-FFM2.ecrc.de!newsfeed00.sul.t-online.de!t-online.de!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl

Without a lot of explaning (I did this some time ago, and the references I 
found are lost to me), the easiest solution to this issue is:

Use the "Debug" menu, and go to "Exceptions..."

Expand the "Managed Debugging Assistants" and uncheck the "Thrown" and 
possibly "User-unhandled" boxes (if using the "Just My Code" option).

All I can remember about it right now is that there is an issue with the 
Managed Debugging Assistant for "Loader Lock". I have never had any problems 
as a result of turning this off.

-- 
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Who is Mighty Abbott?
A twin turret scalawag.

"lotuspro" <lotus...@discussions.microsoft.com> wrote in message 
news:2FF0F5A7-8AAD-4301-A706-8A039A564978@microsoft.com...
>I was wondering... did you ever find a solution to your problem noted in
> point 1: "An error occurred loading this property page". I seem to be
> experiencing the same thing. I've fully uninstalled and reinstalled VS and
> the problem remains.
>
> "Glass Half Full" wrote:
>
>> I've put about 20 hours into just this problem and I'm becoming quite
>> frustrated.
>>
>> From the link you provided I took this file content:
>> ---
>> Windows Registry Editor Version 5.00
>> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
>> "MDA"="0"
>> ---
>> Placed it in a file and ran that file.  Using regedit I see "MDA REG_SZ 
>> 0"
>> in the appropriate location.
>>
>> I bring up visual studio, compile, entry debug, get the same MDA error on
>> the same line as before.
>> No difference, no effect.  As I said in my first note I can disable the
>> LoaderLock exception from the Debug/Exceptions/Managed Debugging 
>> Assistants
>> option, but that just causes the app to hang in the debugger. 
>> Application
>> runs fine outside of the debugger.  Application runs in debug when 
>> compiled
>> and run on a different machine.  Last night I COMPLETELY removed VS2005 
>> and
>> ..NET 2.0 (and other 2005 components), then reinstalled.  Absolutely, no
>> change in behavior.
>>
>> Following the MDA exception I get the following message:
>> "No symbols are loaded for any call stack frame.  The source code cannot 
>> be
>> displayed."
>>
>> Basically, I'm getting an exception that is impossible to turn off but 
>> that
>> comes for nowhere.
>>
>> Other "odd" (likely unrelated) problems with my version of VS2005
>>
>> 1) Tools/Options/Text Editor/C#/Formatting generates a panel with the
>> message "An error occurred loading this property page".
>>
>> 2) When I recompile I see the following warning:
>> Warning 1 'System.Configuration.ConfigurationSettings.AppSettings' is
>> obsolete: 'This method is obsolete, it has been replaced by
>> System.Configuration!System.Configuration.ConfigurationManager.AppSettings'
>> ....
>>
>> ** There is only one problem with this ... THERE IS NO
>> System.Configuration.ConfigurationManager
>>
>> The machine is a Dell that ran VS2003 fine.  VS versions 6, 7 (vs2003), 
>> and
>> 8(vs2005) are all installed on this machine.
>>
>> Help!
>>
>>
>>
>> ""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.
>> >
>>
>>
>>