Yes, you can debug ASP server-side script in VS2003. I do it regularly.
The hard part is not how to debug; it is figuring out how from the
documentation on MSDN. I'll give you a simplified version from memory so if
you can't decipher it, let me know and I'll go through the procedures and
take notes so I can be more specific.
1. Right clicke your project (the project, not the solution) in project
explorer and select properties.
2. On your VS2003 project properties window, debug settings, enable
debugging for ASP files.
3. In IIS manager, either at the default website or the specific site if
you only want to debug ASP in some sites and not in others, click the
Configure button just under the button where you enable the site application.
4. On the configuration applet, there is a checkbox to enable debugging of
ASP pages.
5. Add the appropriate users to the Debugger Users local group. This is
the tricky part, or was for me.
The instructions I followed said to add the IWAM acount to the group, which
didn't work. So then, I added the EVERYONE account, all of the available
network and system accounts, the IUSR account, and my own account. then I
could debug ASP.
Next, I started deleting accounts to see what I could do without. I deleted
the EVERYONE first, deleted all of the NETWORK and system type accounts
except the SYSTEM account since it was already in the group when I started,
and deleted the IUSR account. That left my own account and NT
AUTHORITY\SYSTE M. I debug ASP projects that use anonymous access and that
use Windows Authentication.
At that point, the list seemed reasonably short and I didn't try deleting
any more.
6. Set a breakpoint on server script in your asp files and debug to your
heart's content.
Since the security portion seems to be the hardes part, if my instructions
don't work for you, I suggest you do what I did: add everything under the
sun to the Debugger Users group and start removing until you have a short
working list left in the group.
Good luck.
--
Dale Preston
MCAD C#
MCSE, MCDBA
"Evertjan." wrote:
Bob Barrows [MVP] wrote on 30 dec 2005 in
microsoft.publi c.inetserver.as p.general:
Kyle Peterson wrote: you don't debug classic asp using a debugger..
Actually, if you're lucky (and make the proper sacrifices) you can
debug server-side code with Visual Interdev. I had it working for
awhile... but then it stopped working and I could never make it work
again. It's very susceptible to FrontPage Server Extensions conflicts.
Visual Interdev and Frontpage are often used by people that don't want to
learn indepth ASP, and therefore wish for automatic debugging.
Experience learns that automatic debugging is impossible,
debugging needs manual breakpoints and a good knowledge of a language.
A debugger could detect syntax failures, but the larger part of bugs are
logical errors that only show at runtime and depend on the external input.
Simple, clean and straight forward programming code, which the above
progrmmes don't give, is a prerequisite for a good working and maintainable
code.
--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)