I am trying to debug an .ASP file (yes, that's right, I said ".asp" - not
".aspx") using visual studio .net. I can set breakpoints, but the debugger
totally ignores them. The pulldown list (Release/Debug) is totally empty.
I am trying to "Attach" to the browser process that is running when I browse
to the ASP page in question.


I urgently need to debug this code and it's impossible without breakpoints
etc.....

any ideas? help!!!!


Owen
ps. replies cc'd via email appreciated
owen.southwood@mantix.com

Hi owen,

Firstly we want to know how do you import your asp file into the VS.NET
environment?

Do you have added that ASP file into a existing ASPNET project?
If so, you should enable the "Project\Properties...\Configuration
Properties\Debugging\Debug\Enable ASP Debug" option, and then you can debug
the ASP file in the VS.NET IDE directly by F5...

By the way, if you have the Visual InterDev 6.0, we suggest you had better
debug ASP file in it:
Microsoft Visual InterDev 6.0 Debugging
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvid/html/
msdn_videbugging.asp


Thanks!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

[quoted text, click to view]

Yes.

[quoted text, click to view]

No.

Doesnt work.

[quoted text, click to view]

Doesnt work.

I have also tried debugging as a separate file (not a project) in both
environments by attaching to the browser process. Doesn't work either.

Hi Owen,

Thanks for the reply. As for the problem you mentioned, I'd like to confirm
the following things:
1. What's your development enviorment, the OS's version(server or personal)
and the IIS version(5 or 6)?

2. Can you correctly debugging asp.net web application via VS.NET ide?(BOTH
F5 and manually attach). If so, we can focus on the problem on CLASSIC ASP
debuging.

As for the asp debuging, we can current try the following steps:

1. Check your web application(which contains the asp pages)'s IIS virtual
folder security setting. Are you allowing anonymous access and using
windows authentication?

2. Check the account you log on that machine, is it in the administrators
group and the Debuger User group?

3. Try creating a new asp.net web application and create a simple asp page
in it. Add some lines of code and add a break point. Make sure the
project's "Enable ASP Debugging" is enabled and set the asp page as start
page , F5 debug. IF can't debug , is there any error info?

In addition, as for ASP, the serverside script code's executing is not in
the browser's process. They're processed in the IIS's process( DllHost on
win2k server(or xp) , W3wp on win2k3). So attaching to the browser
process will not work.
However, based on my local testing, I've been able to use F5 debuging on
asp pages in my asp.net project. (looking at the VS.NET's output window, it
actually did attach the DLLHOST(or w3wp on w2k3 iis6)). However, when I
manually attach the process, the break point will never be hit.
Regarding on this point, I'll consult some further experts to see whether
this is a known behavior, and I'll update you as soon as I got any new
information.

Thanks for your understanding.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Hi Owen,

After some further consulting, there dosn't seem have any existing issue on
debuging CLASSIC ASP in VS.NET IDE though this is not the main debugging
function of vs.net. Have you checked the things in my last reply or have
you got any progress on this issue? If you have any problems or need any
further assistance, please feel free to post here. Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)