Visual Studio 2010 Beta 2: The Historical Debugger is now IntelliTrace!

Over the last few months, I’ve blogged a fair amount about a new feature in Visual Studio 2010 called the Historical Debugger. With the announcement of Visual Studio 2010 Beta 2 also comes a name change for the Historical Debugger. It is now called IntelliTrace™. Background: We literally spent over two years agonizing over the…


How to edit code when debugging a 64-bit application

One of the most popular features in the Visual Studio debugger is the ability to edit code during a debug session and have the changes apply without having to stop the debugger, recompile the application and then run the application to verify the changes. This feature is affectionately known as "Edit and Continue" or "E&C"…


RUNTIME turns 100,000!

Today represents a huge personal milestone. My car reached a 100,000 miles! There is nothing unique or special about my car except the license plate and the Visual Studio logo on the hood. Most of my friends refer to the car as RUNTIME (for obvious reasons). I purchased it when I first joined Microsoft from…


Debugging a COM object (Runtime Callable Wrapper) with Visual Studio 2010

If you have written managed code that uses a COM object, then you are probably familiar with System.__ComObject. When a COM object lacks a Runtime Callable Wrapper (RCW), the CLR provides a generic RCW which is an instance of the type "System.__ComObject". Unfortunately, one of the downsides to System.__ComObject is that the Visual Studio 2008…


Coverage of the Visual Studio 2010 Historical Debugger

During the last couple of months, I’ve covered the Historical Debugger extensively. If you are interested in learning more about this new feature in Visual Studio 2010, the following blog entries should help you get started. An in depth look at the Historical Debugger in Visual Studio 2010 (Part I) An in depth look at…


An in depth look at the Historical Debugger in Visual Studio 2010 (Part VI)

In previous blogs, I have covered the Historical Debugger extensively and talked about many of the scenarios. In this post, I’ll walk through another scenario where the Historical Debugger is very useful which is Load Testing. When loading testing an application, you can have the Historical Debugger collect information during the run and if one…


Class Breakpoint: How to set a breakpoint on a C++ class in the Visual Studio Debugger

When debugging an application, there are times when you want the debugger to stop whenever any of the functions in a particular class are called. An example of this may be when you are trying to find out which object is calling your class. Of course, you could manually set a breakpoint on every function…


Troubleshooting common breakpoint problems in the Visual Studio debugger (Part I)

On the Visual Studio debugger team, one of the areas where we regularly receive feedback is when breakpoints don’t work. Furthermore, some of the error messages that the debugger displays when a breakpoint fails are generic so it might be hard to diagnose why a breakpoint doesn’t work correctly (we’re working to improve these error…


How to debug a 64-bit dump using the Visual Studio debugger

One of the questions that comes up about debugging dump files is how to debug a dump file that was created from a 64-bit process. The reason why this question comes up is because Visual Studio itself is a 32-bit application and therefore, cannot debug a 64-bit dump file (or process). As a result, the…


A few facts about the DinnerNow.net 3.1 sample application

Now that the DinnerNow.net 3.1 sample application has been released, I thought I’d share some information about the project to help developers learn more about DinnerNow.net and what they can expect after downloading it. The following table summarizes the artifacts (source code, images, et.c) that make up the DinnerNow.net 3.1 sample application. DinnerNow Artifact Count…