Re: Debugging classic ASP in VS.Net 2003

• Previous message: m11533: "Watch byte array display form"
• In reply to: cathyt: "Debugging classic ASP in VS.Net 2003"
• Messages sorted by: [ date ] [ thread ]

Date: Sun, 14 Nov 2004 00:33:20 +0100

Hi Cathy!

I just succeeded in doing exactly what you're trying to accomplish, helped
in part by the info in your post. It's only fair that I try to help you
back. :-)

The following are important, AFAIK:

- Web.config debug=true
- Project... Properties... Configuration... Debug... ASP and ASP.NET
debugging are both checked

In addition to that, have you followed the steps given in the link below (a
page titled "ASP Remote Debugging Setup")?

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxtskaspremotedebuggingsetup.asp?frame=true

I did that before reading your post, discovering the "Enable/ASP debugging"
project option, so I cannot be completely sure the steps given in the URL
above are absolutely necessary, but I followed them and debugging of classic
ASP now works like a charm. I have only done it locally so far, BTW.

I have not touched any settings at all for IIS, but I'm running under Win XP
so I'm not using the same IIS version as you. It could be that some default
settings have changed I suppose.

Also, when I debug my app I don't attach to any existing process, I just
start my project in debug mode from within VS.NET by pressing F5.

On a more technical note, I don't think you're likely to find any relevant
information about "exporting symbols" from ASP pages etc. ASP pages consists
of script code and are not compiled. The "symbols" are thus readily
available directly in the .ASP files. Symbol info files (PDB) and similar is
more applicable for compiled modules written in C++, VB.NET, C#, etc.

Good luck!

/Emil

"cathyt" <cathyt@berkeley.edu> wrote in message
news:17f6bc12.0411100823.511a2336@posting.google.com...
>I am trying to debug a classic ASP application LOCALLY in Windows 2003
> server, IIS6, VS2003. This is a working application that is being
> migrated to W2003/IIS6.
>
> I can successfully debug a test ASPX file in this particular project
> and the debugger will stop at the breakpoint I set, but when I set a
> breakpoint in any ASP file in the same project, I get the question
> mark inside the breakpoint red circle with the message "The breakpoint
> will not currently be hit. No symbols have been loaded for this
> document." and the code does not stop at the breakpoint.
>
> Do .asp files need debug symbol files? If so, where are they?
>
> My settings:
> IN VS.NET
> Web.config debug=true
> Solution... Properties... Common Properties... Debug Symbol Files --
> it's blank
> Project... Properties... Configuration.. Build .. Generate Debugging
> Information is checked
> Project... Properties... Configuration... Debug... ASP and ASP.NET
> debugging are both checked
>
> IN IIS
> IIS ... Application... Configuration... Debugging... Enable ASP Server
> side debugging is checked
> IIS ... Application... Mappings... I added DEBUG to the verbs for ASP
> (GET,HEAD,POST,TRACE,DEBUG)
>
> DIFFERENCE BETWEEN ASPX and ASP RESULTS:
> A test aspx file in this project stops at the breakpoints
> 3 dlls show up in the module window with the message "Symbols loaded"
> all other dlls show up with "No symbols loaded"
> A test asp file in this project doesn't stop at the breakpoint (which
> is the first line of code) -- the message at the breakpoint (red dot
> with question mark) is "The breakpoint will not currently be hit. No
> symbols have been loaded for this document."
> All of the dlls in the Modules window show up as "No symbols loaded"
>
> In both the asp and aspx tests, the w3wp.exe process is attached.
>
> Many thanks to anyone who can help me with this.

• Previous message: m11533: "Watch byte array display form"
• In reply to: cathyt: "Debugging classic ASP in VS.Net 2003"
• Messages sorted by: [ date ] [ thread ]