|
|
The pessimist sees the glass as half empty; the optimist sees the glass as half full; the programmer sees the glass as twice as large as it needs to be.
—Anonymous
Asp is just web pages. Those are so simple there shouldn't even be a need to debug them at all, right? Well, that's what a lot of people seem to think, at least. ASP scripters never got any respect from "real" developers, who couldn't get past the reaction, "He's just writing a web page—how hard could it possibly be?"
How hard, indeed. The thing most non-ASP developers never understood was just how limited the debugging tools for ASP were. Based on the state of ASP debugging tools, you almost got the impression that Microsoft never really expected ASP to be used for anything more complicated than
<%@ LANGUAGE=VBScript%>
<HTML>
<BODY>
Blah blah blah. Today's date is <%= Now()%>.
</BODY>
</HTML>
By contrast, ASP.NET was designed from the ground up to be a full-featured development platform that can handle almost any task you throw at it. You'll find ASP.NET applicable for far more things than ASP. Thankfully, you'll also find debugging ASP.NET pages to be a much more pleasant task, too.
In this chapter, we'll talk about some of those advances that make ASP.NET so much easier to debug. We'll also discuss some ASP.NET debugging features that can be used to debug traditional applications as well, such as the ability to detach the debugger from a process and using the VS.NET remote debugger. Finally, since many ASP.NET pages often access a SQL Server database, we'll examine some of VS.NET's new support for debugging SQL Server stored procedures.
|
|