.NET news » Debug

With Microsoft SQL Server 2000 it was possible to debug stored procedures from directly within Query Analyzer (see Debugging a SQL Stored Procedure from inside SQL Server 2000 Query Analyzer for more information). With SQL Server 2005, however, this functionality was moved out of SQL Server Management Studio and into the Visual Studio IDE. Using this technique, it is possible to step into your stored procedures, one statement at a time, from within Visual Studio. It is also possible to set breakpoints within your stored procedures' statements and have these breakpoints hit when debugging your application.

All editions of SQL Server 2005 include debugging support (including the Express Edition). However, only the Team Systems and Professional editions of Visual Studio enable stored procedure debugging from within the IDE. In short, if you are using Visual Web Developer or Visual Studio Standard Edition then you cannot step through a stored procedure or enter the stored procedure via application debugging.

In this article we will examine how to debug SQL Server 2005 stored procedures through the Visual Studio IDE. We will look at both stepping into a stored procedure directly from the IDE as well as how to set breakpoints within the stored procedure that are then hit when debugging the application.

Event Tracing for Windows (ETW) provides general-purpose, high-speed tracing of events raised by both user-mode applications and kernel-mode device drivers. Learn how ETW can improve your development and debugging work.

An extremely easy to use and incredibly fast tracer with lots of options.

When is the .NET Garbage Collector unable to reclaim memory? The answer might surprise you. Stay tuned.

Modifies .NET MSIL binaries to call configured methods at the beginning and end of methods in the binaries.

Explains how to debug ASP.NET application by using breakpoint's advantages.

Provides an easy-to-use "drop it in" Exception logging framework for ASP.NET 1.1 and 2.0 applications. Log to a database, receive an email with a description and a link to the reporting page with the exact exception, and even optional Syslog reporting. Complete article with source code downloads. Uses the new "Data" field in the .NET 2.0 Exception class.

This article presents a simple .NET 2.0 event logging class. It is designed to allow multiple threads to add events to one or more log strings and provides event driven updates for viewers.

Don't build logging capabilities for your applications from scratch; you can get robust and flexible logging functionality for your .NET applications with the free open source log4net framework, and then extend it to support custom needs.

The latest releases of WinDBG and Visual Studio know exactly how to use source server, so its benefits are available to both .NET and native C++ developers. See why this is so important in tracking down bugs.