Re: Debugging ASP and VS2005

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

"davidm" <davidjmcdonough@xxxxxxxxxxx> wrote in message
news:1150739936.939932.18640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I having trouble debugging (in VS2005) a classic ASP application that
calls a VS2005 class library.By setting the breakpoint in the ASP code
and using code type, script, and attaching to the dllhost.exe (using
IIS 5.0), I can break and debug in the ASP code (that I initiated
outside of the VS2005 IDE by calling http://localhost/XXX.asp in IE).

When I set the breakpoint in the VS2005 class library and set the code
type to managed (or anything else) I cannot get the managed code to
break. My class library is part of a solution that contains a Windows
application that is my start up project.

On the breakpoint in the managed code I get the message "Break point
will currently not be hit. No symbols have been loaded."

Configuration of all projects in solution Debug.

(I would have though debugging the script would have been more
difficult than debugging the a managed code).

Any help appreciated.



.

Quantcast