CODEWITHSUNDEEP
visual-studio-2008asp-classicvisual-studio-debuggingiis-8
user48408
user48408

Reputation: 3354

Debugging Classic asp Visual Studio 2008 IIS 8

Things I've done: On both the default website and my virtual folder in IIS Manager

-Enabled Parent Paths

-Set Enable Server Side Debugging to be True

Set Breakpoints in my code by 1) F9 2) Using the Stop command 3) Purposefully put mispelled commands in my VBScript to force the debugger to attach

I've then tried starting the website without debugging and attaching to W3wp.exe/ DLLHost.exe

Have also tried running the website in visual studio in debug mode

Is there something I'm missing or worth trying?

Upvotes: 0

Views: 1301

Answers (2)

user48408
user48408

Reputation: 3354

I was almost there but when I went to attach to process, selecting w3wp.exe, I needed select the code types I was trying to debug and make sure the Script checkbox was selected

Upvotes: 1

Erik Oosterwaal
Erik Oosterwaal

Reputation: 4374

Try setting "send errors to browser" to TRUE in your application pool, and if that still doesn't work "Enable client-side debugging" to TRUE.

Also, I've seen some some issues on SO lately involving the debugger not kicking in when the client is IE10 (which is weird).
The solution there was to change a registry setting. It seems that installing IE10 messes up the link between the debugger and ASP. Maybe IIS8 does the same. Here is some more info, maybe it helps you:

http://blogs.msdn.com/b/yash/archive/2007/09/20/debugger-not-working.aspx VS2010 and IE10 Attaching the Script debugger to process iexplore.exe failed

Another solution suggested (besides the registry setting) was to install VS2012 (the free edition is enough) to restore the link between the debugger and the server.

HTH. Erik

Upvotes: 0

Related Questions