Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Debug with Microsoft Development Environment

Status
Not open for further replies.
Nov 8, 2005
25
CA
Hi there

Before I was able to use Microsoft Devleopment Environment to debug my asp code. I did that by going to Microsoft Development Environment 6.0, go to Debug menu -> Processes, and will see inetinfo.exe and then I can attach it.

But lately, (and I don't know if it's got anything to do with the fact that I have recently installed Norton Internet Security and Norton Anti Virus) when I opened the Processes window, the list is blank, and the Machine drop down is also empty. If I hit Properties or Refresh, I'll get the
"Development Environment has encountered a problem and needs to close. We are sorry for the inconvenience" error, and the app will close.

If I hit the Machine button, even if I find the machine, it'll say "Unable to connect to the machine"

Has anyone had similar problems before? It's hard not to be able to debug ASP pages.

Anyway, I finally uninstalled the whole Norton Symantec crap off my computer. And I went to try the debuuger again, and again nothing shows up in the dropdown list. So therefore I don't even know if this problem originated from Norton or not. One thing I know for sure, I'm very frustrated, just the same.

Thanks
CC
 
You can do a search for other threads in this forum but I do believe there are documented problems elsewhere in the forum discussing how Norton has screwed around with the debugging (among others) functionality. Even taking it off the machine may not have fixed it because there may be registry settings that have also changed (and not changed back when you took it off). You may want to reinstall everything. Another option is that you can also debug ASP files by writing a response.write and then response.end commands to see where you may be hitting issues. It's a little less efficient than being able to debug in the manner in which you're already accustomed (I've had similar issues), but it will still get you what you need. Hope that helps.

------------------------------------------------------------------------------------------------------------------------
"Men occasionally stumble over the truth, but most of them pick themselves up and hurry off as if nothing ever happened."
- Winston Churchill
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top