Re: Can't debug Classic ASP In VS.NET 2005

Tech-Archive recommends: Fix windows errors by optimizing your registry

I found this after googling the problem. I wish I would have tried that
sooner. *bonk self*

http://blogs.msdn.com/mikhailarkhipov/archive/2005/06/24/432308.aspx

This seems to work with my system, only I attached to the dllhost.exe
(instead of w3wp.exe because I'm running IIS 5.0) running under the IWap
User Name. It gave me a warning, and asks if I want to attach to this
process, I clicked the 'Attach' button and my break points were hit. Yay!

I hope this help you!
Velvet

<kaczmar2@xxxxxxxxxxx> wrote in message
news:1148328628.495487.99470@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hey there,

I have an issue where I cannot debug Classic ASP pages in VS.NET 2005.
I don't get an error message (ie, breakpoints will not be hit), no
application event log errors, anything.

I have my IIS application security set to medium (so I will attach to
dllhost instead of inetinfo.exe.

1) I start the debugger
2) once the application is up, I select Attach to process.... and pick
dllhost.exe (script, t-sql, x86) which is running under IWAM account.

navigate to the page with the breakpoint. It is not hit. This is the
same for all projects within VS 2005 - it is not project specific.

I have done this on 10 other machines with the same configuration and
every one works. I can hit breakpoints. (attaching both to dllhost.exe
or inetinfo.exe, depending on Application security settings.)

I have checked all reasonable settings against other machines and
everything looks identical

No error messags in the immeditate window, nothing.

Does any one have any insights. If anyone has had this issue and
gotten past it, could you please let me know. I appreciate your help.

Christian



.

Quantcast