Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I just wanted to say that you guys RULE, a million thank you's to whoever created, and/or manages this site. KEEP UP THE GOOD WORK..."

Geography

Where in the world do Tek-Tips members come from?

Debug with Microsoft Development Environment

calgarychinese (MIS)
20 May 06 19:16
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
Chopstik (TechnicalUser)
22 May 06 16:02
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

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close