HOWTO: Remotely debug classic ASP in Visual Studio 2005

After reading

http://www.devx.com/tips/Tip/18204
http://support.microsoft.com/kb/q258929/
http://www.gotdotnet.com/team/csharp/learn/whitepapers/How%20to%20debug%20script%20in%20Visual%20Studio%20.Net.doc
http://www.odetocode.com/Articles/425.aspx
http://groups.google.com/group/microsoft.public.vsnet.debugging/browse_frm/thread/fb2ff0a3112d57f1/ef6d09432ab9edb8?lnk=st&q=debug+asp+%22visual+studio+2005%22+attach&rnum=2#ef6d09432ab9edb8

and dozens of other articles, i am still no closer to being able to debug
ASP. The only one that looks like it was written by someone who knows what
they were talking about was the Word document from GotDotNet, so i'll go
with that. Here are the modified steps i've taken so far.

NOTE
1. ASP not ASP.NET
2. Running on a remote machine
3. The remote machine is Windows 2000
4. The remote machine is running IIS 5
5. The web-site using a host header name
6. The web-site's "Application name" is the default of "Default Application"
7. The web-site's "Application protection" level is set to "High (Isolated)"


Steps That Don't Work
==============
1. Open IIS Manager
1a. (Start->All Programs->Administrative Tools->Internet Information
Services)
1b. Connect to, or expand, the web-server running the web-site is you want
to debug.
1c. Expand "Web Sites"
2. Right-click the web site you want to debug and select Properties.
3. Go to the "Home Directory" tab
3a. Click the "Configuration" button
NOTE: If nothing happens, then you are running Internet Information Services
from a machine that is not the same as the server. You must run IIS manager
locally on the server itself. Install a program like WinVNC on the server so
you can run Internet Information Services from the server's own desktop -
and not remotely.
4. Go to the "App Debugging" tab
4a. Check the "Enable ASP server-side script debugging" checkbox.
NOTE: i don't know what this check-box actually does, but not to worry,
nobody really does.
4b. Check the "Enable ASP client-side script debugging" checkbox
NOTE: i dont' know what this checkbox actually does, but not to worry the
help says "This check box is reserved for future use and has no effect on
the current version of ASP." So nobody knows what this checkbox really does.
5. Reset IIS so that the setting will be applied.
NOTE: i don't know if you have to only stop and start your web-site, or if
you have to stop and start IIS service, or if you have to reboot the entire
machine. Best to reboot the whole machine to be safe.

6. Launch Visual Studio 2005
6a. (Start -> All Programs -> Microsoft Visual Studio 2005 -> Microsoft
Visual Studio 2005)
6b. By default no "Debug" menu item will be present, in order to access it,
open any file on your computer (e.g. c:\adsf.txt)
6c. File->Open->File...
6d. Select c:\asdf.txt
7. Select the menu option Debug->Attach to Process...
8. Leave Transport at its default "Default"
9. Change Qualifier to the name of the name of the web-server machine.
10. Select the process that the web-site will be running as
This could be one of:
DLLHOST.EXE
inetinfo.exe
or perhaps some other process name
NOTE i cannot tell you want process your web-site will run as.
10a. If your application is running under Low Security, it should be running
as inetinfo.exe
10b. If your application is running under Medium or High Security, it should
be one of the DLLHOST.EXE's running. But not all of them are web-sites, and
not all of them will be the web-site you want.

11. The process you want to attach to will have a Type of "Script" in the
listview.
12.-47. [omitted]
48. Profit.


None of the process's listed on my machine have "Script" option available.
So now what?

There is no "Script" option for attaching to the script host
===================================
The Word document has a large and detailed list of troubleshooting tips if
there is no "Script" option for attaching to the script host.
1. Make sure the user account the script host is running under is part of
the Debuggers Users group.
1a. What process is the script debugger running under? Is it the same as the
random process from step 11 above?
2. regsvr32 pdm.dll
2a. regsvr32 scriptle2.dll
3. Restore your default DCOM settings (delete
HKLM/Software/Microsoft/Ole/DefaultAccessPermission)

So, now what?

The steps listed above are most of the steps i've actually tried. i left out
steps such as
- install Windows 2000 server
- install IIS on Windows 2000 server
- install Windows XP on my desktop machine
- develop a web-site
- install Visual Studio 2005 on my desktop machine

Other articles talk about other things, like FrontPage, remote debugging
tools, COM+ settings, registry keys, opening solutions in Visual Studio
2005, TCP/IP or named pipes, NTLM authentication, etc. i didn't follow
these, since they seem to not be for what i want. i want to debug ASP.



Additionally, can anyone tell me which groups i should cross-post to when i
ask again in a month and a half?


.