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

4 (7 votes)

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).

You might also like...

Date Posted:
Last Updated:
Posted by:
Total Views to date: 20692

2 Comments

- 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

- 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.

Recent Comments

Gfw 03/02/2017 09:48
In response to Free SSL Certificates On IIS With LetsEncrypt
I have used WinSimple for about the last 9 months - works great. One thing that you want to make of...

Ted Driver 02/02/2017 13:24
In response to Free SSL Certificates On IIS With LetsEncrypt
This looks great is you have command line access to your web server - what about those of us on Is...

Carl T. 06/11/2016 05:43
In response to Server.MapPath Equivalent in ASP.NET Core
Very succinct and easy to follow. Worked perfectly the first time for me. Thanks!!...

Manoj Kulkarni 04/11/2016 05:47
In response to Entity Framework Core DbContext Updated
Great post....

Sivu 19/10/2016 08:21
In response to Entity Framework Core TrackGraph For Disconnected Data
Oh that's very very very nice ! Thanks for the write up Mike, much appreciated for the taking the to...

Mark 12/10/2016 16:42
In response to ASP.NET Web Pages vNext or Razor Pages
Although "Web Pages" was removed from the roadmap, has it just been renamed to "Razor Pages"?...

Satyabrata 12/10/2016 09:20
In response to Entity Framework Core TrackGraph For Disconnected Data
Nice article. Please write more articles featuring ASP.Net web pages. Thank you...

Julian 26/09/2016 14:27
In response to Loading ASP.NET Core MVC Views From A Database Or Other Location
Fantastic, many thanks Mike! Had got half way down this road before finding your article - saved...

Abolfazl Roshanzamir 14/09/2016 05:36
In response to Loading ASP.NET Core MVC Views From A Database Or Other Location
Nice article. Thanke you so much ....

cyrus 02/09/2016 15:12
In response to ASP.NET Web Pages vNext or Razor Pages
I've got some news. As Damian stated in this link: https://github.com/aspnet/Mvc/issues/5208 “We...