Co-worker can debug on server but I can't

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Error message: "Unable to start debugging on the web server. Unable to map
the debug start page to a machine name."

I can no longer run the debugger from my local PC for a project on our web
server. You know, F5 in Visual Studio. I can run in debug mode for a
project on my local web server.

The problem began one day about 3 weeks ago when I ran the project in debug
mode and somehow ended up breaking the .NET framework. Thank you Visual
Studio! I was able to repair the framework but I am unable to debug. My
co-worker oddly enough can run the project in debug mode.

So the problem appears to be something with my computer. I am running
Windows XP Pro Service Pack 2. Oh how I long to get back to being able to
debug. Please do not respond unless you really know how to handle this
problem.

Thanks,
Steve
 
Debugging on the server is not the standard modus operandi. Local development
with test on a centralized server is the norm. You then keep code in
conjunction by using a code repository, like SourceSafe.

Remote debugging has been a bear since the ASP days, if not earlier. I am
not sure why you, in particular, are having a problem, but I would recommend
moving to local development, if possible. Even if you get the problem fixed,
you will find that only one developer can debug at a time and any hits to the
pages while you debug will fire off the debugger. Plus, it is far too easy to
break a build when everyone is dinking around with the same code base on the
same server.

---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
Thanks Greg. You are right; I should be doing my development locally where I
can debug no problem.
 
Back
Top