Sign in
Mikhail Arkhipov (MSFT)'s WebLog
Visual Web Developer stuff
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Blog Home
Email Blog Author
Share this
RSS for posts
Atom
RSS for comments
Search
Tags
Personal
Rants
Archive
Archives
June 2012
(1)
July 2010
(1)
January 2009
(1)
December 2008
(5)
June 2008
(2)
April 2008
(1)
March 2008
(3)
January 2008
(1)
December 2007
(5)
November 2007
(3)
October 2007
(4)
September 2007
(3)
August 2007
(3)
April 2007
(5)
February 2007
(3)
January 2007
(3)
December 2006
(7)
November 2006
(3)
October 2006
(2)
September 2006
(2)
July 2006
(4)
June 2006
(4)
May 2006
(7)
April 2006
(8)
March 2006
(5)
February 2006
(3)
January 2006
(2)
December 2005
(6)
November 2005
(4)
October 2005
(3)
September 2005
(1)
August 2005
(6)
July 2005
(2)
June 2005
(15)
May 2005
(3)
April 2005
(6)
March 2005
(2)
January 2005
(7)
December 2004
(3)
November 2004
(1)
October 2004
(3)
September 2004
(4)
August 2004
(13)
July 2004
(6)
June 2004
(16)
May 2004
(15)
How to debug classic ASP pages in VS 2005
MSDN Blogs
>
Mikhail Arkhipov (MSFT)'s WebLog
>
How to debug classic ASP pages in VS 2005
How to debug classic ASP pages in VS 2005
Rate This
Mikhail Arkhipov
24 Jun 2005 2:04 PM
Comments
30
Quite a few people were unable to make VS 2005 to hit breakpoints in the server script in classic ASP pages. Little surprise here since the way we do ASP debugging changed since VS 2003 and there little or no information currently in VS 2005 Beta 2 docs on the topic (I filed a bug on this). Most importantly, setting BP and hitting F5 won't work - breakpoint never binds. Two key items here:
1. Classic ASP debugging only works with IIS. It does not work with the VS Development Web Server (Cassini).
2. In VS 2005 you have to attach to the ASP worker process (w3wp.exe in IIS 6).
Here is how to make ASP debugging work:
1. Enable ASP debugging on the server. (I also added DEBUG verb to the asp extension, but I am not sure if it is required).
2. Open classic ASP in VS 2005.
3. Set breakpoint.
4. View page in browser or run without debugging.
5. Debug | Attach to Process
6. Locate IIS ASP worker process (w3wp.exe on IIS6) which exposes x86 and Script and attach as Script.
At this point breakpoint should bind and you should be able to hit it. You may have to refresh the page in the browser to get the code executed again. I tried on Windows 2003 SP1 Standard Server running IIS 6 and it worked for me. I want to try on XP Pro + IIS 5 next.
30 Comments
Blog - Comment List MSDN TechNet
Comments
Loading...