Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / August 2003

Tip: Looking for answers? Try searching our database.

The debugger is not properly installed. Run setup to...

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
luket - 08 Aug 2003 20:07 GMT
A very strange thing has happened to two installations of
VS.NET on two different machines at two different
locations.

Yesterday I zipped up my project I was working on at work
and FTP'ed it home. I then opened it there, compiled it
and tried to debug it. I then got the message:
"Unable to start debugging."
"The debugger is not properly installed. Run setup to
install or repair the debugger."

I found this to be really odd, because my VS.NET has been
working fine for well over a year.

Anyway, I uninstalled and started a reinstallation of the
product. When I went back to work the next day, I rebuilt
my project there and then tried to debug it. I then got
the same error!
"Unable to start debugging."
"The debugger is not properly installed. Run setup to
install or repair the debugger."

What in the world could have happened such that two
machines in two locations have suffered the same failure??

I've not done any Updates and the machine at work is 2000
and the one at home is XP Pro.

Any ideas?

Best regards,
Luke Tomasello
Chuck D - 09 Aug 2003 14:46 GMT
More than likley, some dll has gotten itself improperly registered, or
overwritten by another.  I had a very similar experience recently with the
server explorer, and it took a great deal of research to find out which
dll's needed to be copied from one directory to another.  As is always the
case with somethign like this, try the microsoft knowledge base first.

Chuck

> A very strange thing has happened to two installations of
> VS.NET on two different machines at two different
[quoted text clipped - 28 lines]
> Best regards,
> Luke Tomasello

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.