Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

Tuesday, November 24, 2009 5:42 PM

Search For This Line In IntelliTrace

One of the key benefits of IntelliTrace is that it collects lots of useful information about your application which allows you to debug exactly what the application was doing when a problem occurred. With so much information, it's important to be able
Posted by habibh | 1 Comments
Friday, November 20, 2009 2:23 AM

IntelliTrace: A graphical comparison

One of the easiest ways to understand what IntelliTrace is and what it does, is through a comparison between how most developers debug their application today vs. what IntelliTrace enables. In the figure below, the blue section labeled (1) shows one of
Posted by habibh | 1 Comments
Tuesday, October 27, 2009 6:30 PM

How to Count the Lines of Code (LOC) in your application using Visual Studio

I was talking to someone the other day and he asked me whether Visual Studio has a tool to count the lines of code in an application. It occurred to me that others might be interested in the answer so I decided to blog about it. There is a tool called
Posted by habibh | 2 Comments
Monday, October 26, 2009 10:23 PM

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
Posted by habibh | 4 Comments
Friday, October 23, 2009 9:30 PM

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
Posted by habibh | 0 Comments
Thursday, October 22, 2009 9:53 AM

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
Posted by habibh | 0 Comments
Wednesday, October 21, 2009 10:05 PM

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
Posted by habibh | 0 Comments
Tuesday, October 20, 2009 7:41 PM

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
Posted by habibh | 0 Comments
Monday, October 19, 2009 9:01 AM

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™.
Posted by habibh | 0 Comments
Monday, October 12, 2009 10:19 PM

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.
Posted by habibh | 0 Comments
Monday, September 28, 2009 9:53 PM

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).
Posted by habibh | 0 Comments
Filed under:
Tuesday, September 22, 2009 12:31 AM

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".
Posted by habibh | 0 Comments
Monday, September 21, 2009 12:04 AM

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
Posted by habibh | 0 Comments
Friday, September 18, 2009 8:48 PM

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
Posted by habibh | 0 Comments
Thursday, September 10, 2009 11:34 AM

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,
Posted by habibh | 0 Comments
More Posts Next page »
 
Page view tracker