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> <uHLnaNA$FHA.3464@TK2MSFTNGP15.phx.gbl> <ud5YamB$FHA.4088@TK2MSFTNGP09.phx.gbl>
Subject: Re: VS 2005 LoaderLock problem
Date: Thu, 8 Dec 2005 14:34:30 -0500
Lines: 101
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; Response
Message-ID: <ONYnr5C$FHA.216@TK2MSFTNGP15.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework
NNTP-Posting-Host: sas12014.nat.sas.com 149.173.12.14
Path: g2news1.google.com!news4.google.com!newshub.sdsu.edu!msrtrans!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
Thanks, that does indeed fix that warning. I feel a bit foolish I missed
that one.
"Kevin Spencer" <ke...@DIESPAMMERSDIEtakempis.com> wrote in message
news:ud5YamB$FHA.4088@TK2MSFTNGP09.phx.gbl...
>> ** There is only one problem with this ... THERE IS NO
>> System.Configuration.ConfigurationManager
>
> You must not have the assembly that has this referenced. That is the
> System.Configuration assembly.
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> You can lead a fish to a bicycle,
> but you can't make it stink.
>
> "Glass Half Full" <sta...@nospam.nospam> wrote in message
> news:uHLnaNA$FHA.3464@TK2MSFTNGP15.phx.gbl...
>> 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.
>>>
>>
>>
>
>
|
