Re: VS 2005 LoaderLock problem
- From: "lotuspro" <lotuspro@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Jan 2006 09:06:31 -0800
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-phuang@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:FaC4sf7%23FHA.552@xxxxxxxxxxxxxxxxxxxxxxxx
> > 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.
> >
>
>
>
.
- Follow-Ups:
- Re: VS 2005 LoaderLock problem
- From: Kevin Spencer
- Re: VS 2005 LoaderLock problem
- Prev by Date: Re: FileNotFoundException when porting from Dev 2003 to Dev 2005
- Next by Date: Finding and Creating Assemblies?!? fuslogvw
- Previous by thread: Re: VS 2005 LoaderLock problem
- Next by thread: Re: VS 2005 LoaderLock problem
- Index(es):
Relevant Pages
|
