Latest Debugging Articles

Software defects and bugs cost $60 billion a year in the US. Check out this infographic to get a few other statistics on the impact of defects in your applications.

In this new installment, you'll discover how to write an even more robust version of a debugger visualizer using WIndows Presentation Foundation (WPF). You'll learn how to visualize additional data types as well as how to change the value of variables.

There are lots of good examples of creating a debugger visualizer for Visual Studio, but one thing that this is common is that all of them are written using Windows form. It is, however, possible to make a debugger visualizer in WPF, and thus display data in a much more sophisticated way using modern technology.

Learn about several features relevant to developers in Visual Studio 2010 and the .NET Framework 4.0, such as parallel programming, XSLT debugging, new ASP.NET features, and new VB.NET and C# features that include the Chart control, XSD Designer, Lambda Expressions, and optional parameters.

Code is run in a debugger for two main reasons: examining the branches of code that are being executed, and examining data values to determine why the code is behaving in a certain manner. Inspecting data values can be significantly improved by customizing the debug information. See how that can be done in the Visual C++ debugger.

Are you tired of hard-coding function names in trace messages? Have you ever used cut and paste to copy a trace statement and forgot to change the function name? There'll be no more wild goose chases because of bad function names when you determine the function name dynamically.