Debugging Classic ASP pages in Visual Studio 2005 on Windows XP Pro

As an ardent Dreamweaver user for classic ASP, I used to debug my scripts with a plethora of Response.Write and Response.End statements, outputting the values of various values to the browser to check that logic was working as intended. However, I recently discovered how to use the VS 2005 debugger to make debugging classic ASP (almost) a joy.

This information is accumulated from a number of blogs, chief among them that of Mikhail Arkhipov.

IIS 5.1 on XP Pro doesn't support multiple web sites by default. So the first thing I did some time ago was to download IISAdmin from JetStat which, while it still only allows one site to run on the server at any one time, permits you to create multiple sites. This is fantastic, as it allows you to create site structures that will mirror the hosting environment, and negates the need to run individual projects by adding the folder name to the http://localhost url. Now to add debugging.

  1. First, use IISAdmin to Start the site you want to debug

  2. IISAdmin
  3. Then click on Console to bring up the IIS Management tool and go to the properties of the selected site

  4. IIS
  5. Click the Configuration button on the Home Directory tab and then make sure that "Enable ASP server-side script debugging" is selected (ticked) on the Debugging tab

  6. Enable ASP server-side script debugging
  7. Open the site from within VS, and set breakpoints in the page you want to debug.
  8. Open a browser and browse to the page.
  9. Back in VS, click the Debug menu, and select "Attach to Process..."
  10. Make sure that the "Attach to..." option says "Script". If it doesn't, click the "Select.." button and choose "Script"
  11. Look in the list of processes for dllhost.exe. If it is not there, check "Show processes from all users" If there is more than one entry for dllhost.exe, select the one that has a "Type" entry for "Script, x86". Just to be doubly sure, this should be the entry running under the machinename/IWAM_machinename user. Select this entry and click "Attach". You should get a warning dialogue. Read it and click "Attach" anyway.

  12. Attach To Process
  13. Now go back to the browser, and re-run the page. Debugging should start.

Troubleshooting

If your breakpoints fail to get hit, double check that you have enabled ASP server-side script debugging for the site (Step 1).
If no breakpoint is hit, and the breakpoint markers change from a deep red and hovering over them produces a tool tip saying: 'The breakpoint will not currently be hit, no symbols have been loaded for this document', check that the Attach to... option is Script (Step 7).

Date Posted: Friday, August 17, 2007 10:28 AM
Last Updated:
Posted by: Mikesdotnetting
Total Views to date: 18143

2 Comments

Friday, September 25, 2009 4:46 PM - Marc

Nope it doesn't work at all because there's no dllhost executed in the tasks list and I did try to attach to w3wp OR iexplore and none of them works either

Saturday, September 26, 2009 8:36 PM - Mike

@marc,

I think you mean that you are having some difficulty. It does actually work. The images were taken from screen dumps I made while I was getting it to work. What "Tasks list" are you talking about? I never mentioned anything about a tasks list.
Add your comment

If you have any comments to make about this article, please use this form to do so. Make sure that your comment relates specifically to the article above. More general comments can be posted through the form on the Contact page.

Please note, all comments are moderated, and some may not be published. The kind of things that will ensure your comment is deleted without ever seeing the light of day are as follows:

  • Not relevant to the article
  • Gratuitous links to your own site or product
  • Anything abusive or libellous
  • Spam
  • Anything in a language I don't understand including gibberish.

I do not pass email addresses on to spammers, so a valid one will assist me in responding to you personally if required.

Recent Comments

Allen Michaels 12/17/2014 4:37 PM
In response to Cascading DropDownLists with jQuery and ASP.NET
Fantastic thank you so much!...

Emily 12/17/2014 12:36 PM
In response to Parameterized IN clauses with ADO.NET and LINQ
Thanks, very helpful!!!! Can i use this for multiple in's ????? IN (.....) and IN(...) and IN...

sss 12/16/2014 3:06 PM
In response to Solving the Operation Must Use An Updateable Query error
good...

Gjuro 12/15/2014 10:30 PM
In response to Examining the Edit Methods and Edit View
You have one fromr (and it should be from, I suppose). :-)...

Gjuro 12/15/2014 10:27 PM
In response to Adding Search
Hi, thnx for all this C#->VB translations. Yet, the following code block is (slightly) in error it a...

Scot 12/14/2014 1:39 PM
In response to Entity Framework 6 Recipe - Alphabetical Paging In ASP.NET MVC
Thanks,Mike I found solution....

Gjuro 12/13/2014 10:52 PM
In response to Accessing Your Model's Data from a Controller
The article mentions "Creating an Entity Framework Data Model for an ASP.NET MVC Application" (at is...

Samuel 12/13/2014 8:40 AM
In response to Displaying The First n Characters Of Text
I have failed to use the extension because it throws an error that it doesn't recognise the chop be...

Ignas 12/12/2014 5:11 PM
In response to Cleaner Conditional HTML Attributes In Razor Web Pages
Any suggestions for Html Helper elements with HtmlAttributes, when you need to conditionally set it...

Gautam 12/11/2014 8:50 PM
In response to Validation In Razor Web Pages 2
Hi Mike Is this required for V3, non html helper input...