Microsoft.Net Debugging and Tools (.Net Debugging Series)

Debugging is one of most common activity that every developer has to deal with in its day to day development life cycle. So It is very important that one should know the proper debugging technique and also could use the correct tools for debugging that particular issue.

But quite often it happens that developers are using wrong tools trying to investigate a particular problem. Sometimes developers are lucky to identify the exact place of code for the problem. And some times in spite of extensive code review still the problem is not caught because may be they are looking at wrong place or incorrect tool/no tool is used for debugging.

There are many powerful and free investigative tools which can dramatically reduce the troubleshooting time. These tools are very efficient and used by most of the professional developers. As fact we should know that a single tool can not address the every problem as each of these tools focus on a specific category. So knowing when and how to use each tool is very important for debugging .net applications.

Debugging Tools for Windows

URL: www.microsoft.com/whdc/devtools/debugging/default.mspx

Debugging Tools for Windows 32-bit Versions
Debugging Tools for Windows 64-bit Versions

There are three user mode debuggers available in the Debugging Tools for Windows package—NTSD, CDB, and WinDbg—and one kernel mode debugger (kd). Although these debuggers are three separate tools, it is important to understand that they all rely on the same core debugger engine. The most significant difference between the debuggers is that WinDbg has a graphical user interface (GUI) component, making it easier to work with when doing source level debugging. In contrast, NTSD and CDB are purely console-based debuggers. The snippets of debugger conversation that will be outlined in the book are all captured using NTSD.

After choosing the flavor of the debugger (32-bit or 64-bit), the installation process for Debugging Tools for Windows is straightforward and the default installation options are typically sufficient. The default installation path is

%programfiles%\Debugging Tools for Windows

here are several versions available for download. I have used version

Working and Debugging with .Net Framework 2.0

.Net 2.0 SDK Path: (%programfiles\Microsoft.net\SDK)


Posts By Month