Groups | Blog | Home
all groups > visual studio .net setup > december 2005 >

visual studio .net setup : Corrupted Debug Files


Fred Chateau
12/9/2005 2:36:30 PM
A few months ago I installed Visual C# Express on my computer. I don't
remember whether it was RC-1 or RC-2 but after a week or so I tried to
remove it and had difficulty doing so. I followed recommendations on MSDN,
including running a registry tool specifically designed to handle the
clean-up problems caused by the release candidates.

Eventually I wound up doing a complete repair of VS.NET 2003 Enterprise
Edition in order to restore the file associations as well as other minor
problems. I thought I had it fixed until an application program error
launched the "Select Debugger" dialog which still contained a reference to
VS.NET 2005. More importantly, the VS.NET 2005 debugger seems to run but the
VS.NET 2003 debugger is not working.

I haven't tried debugging within the VS.NET 2003 environment yet, but I'm
assuming it's not going to be reliable since it appears some of the debug
files have been replaced with the newer version. (In other words, it appears
the new version was not a side-by-side install.)

So, do I need to locate all of the debug files on the machine and copy the
older version back?

Or will the newer version operate reliably within VS.NET 2003?

Is there an install/uninstall script to handle all of this or am I going to
have to delete/replace registry entries?

What a mess . . .

--
Regards,

Fred Chateau
fchateauAtComcastDotNet

Fred Chateau
12/10/2005 11:17:52 PM
Well, never mind...

It appears that the reason the VS.NET 2003 debugger and the CLR 1.1 debugger
are not running is because the error is occurring in a .NET 2.0 application.

I was able to step through a .NET 1.1 application within VS.NET 2003 and I'm
assuming the CLR 1.1 debugger would run when selected from the "Launch
Debugger" dialog if the application used the .NET 1.1 assemblies.

Also, I'm now thinking the CLR 2.0 debugger was probably set up during
installation of the .NET Framework 2.0 SDK rather than as part of Visual C#
Express and that's why it remains after uninstalling VC# Express.

Regards,

Fred Chateau
fchateauAtComcastDotNet


[quoted text, click to view]

AddThis Social Bookmark Button