Looking for questions or feedback on IntelliTrace

During the last few months, I’ve been blogging extensively about a new Visual Studio 2010 feature called IntelliTrace (formerly known as the “Historical Debugger”). We are very excited about IntelliTrace and think that it’s going to change how people debug their applications. Since IntelliTrace is a brand new feature, we are eager to hear from…


Using IntelliTrace to view the return value of a VB or C# method

A few months ago, I blogged about how to view the return value of a C# or VB method in the Visual Studio debugger. As I explained in that blog post, the debugger does not support viewing the return value of a .NET method, so you have to apply a workaround or two. Being able…


IntelliTrace is not available. Why?

When using IntelliTrace, you might run across the following error message in the IntelliTrace window: IntelliTrace is not available. See the Debugger Output window or the Windows Application Events Log. Below is a list of reasons why you might see the above error message when trying to use IntelliTrace. 1) In Visual Studio 2010, IntelliTrace…


The future of debugging is here! Visual Studio 2010 now supports stepping back in the debugger.

In my previous post Getting Started with Visual Studio 2010 IntelliTrace: Hello IntelliTrace!, I described how to use the new IntelliTrace feature in Visual Studio 2010 to debug an application. But there’s more to IntelliTrace. IntelliTrace also allows you step back in the debugger! However, the step back functionality isn’t enabled by default. You can…


Getting Started with Visual Studio 2010 IntelliTrace: Hello IntelliTrace!

One of the most talked about features in Visual Studio 2010 Beta 2 is IntelliTrace. In a nutshell, IntelliTrace allows a developer to record the application execution and play it back. Using IntelliTrace, a developer can do some cool things like step back in the debugger. In this blog post, I’ll do a "Hello World!"…


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"…