Monday, May 6, 2013


IntelliTrace is a tool available in Visual Studio which gives developer the facility of record the data of their debugger session. It provides options for developer to rewind the debug & see what exactly happening in the code. In traditional F10 & F11 debugging it gives the very limited data on history data of the debugging session so that we have to re-debug the code in a case where we missed anything. This IntelliTace can be defined as a time machine because it enables the developer to travel through the debugger session data.

IntelliTrace Collects Data On

  1. IntelliTrace events

  2. Method calls and exit points

  3. Breakpoints & Tracepoints

IntelliTrace also allows you to debug the errors in the production environments where you do not have visual studio installed. I’ll provide more details on that in my next post.

Step 1: Open IntelliTrace Settings

Debug –>IntelliTrace –>Open IntelliTrace Settings

Step 2: Configure Intellitrace Settings

Debug –>IntelliTrace –>Open IntelliTrace Settings –> General

By default in setting option of “Intellitrace events only” is selected. If you want the Intellitrace to record the method calls select the second option.


Debug –>IntelliTrace –>Open IntelliTrace Settings –> Advance

Here you can set the maximum size of the each recording. Also you can specify any custom file path to create the log.


Debug –>IntelliTrace –>Open IntelliTrace Settings –> Intellitrace Events

Here you can select the type intelliTrace events you want to record so that you can get more customize & meaningful trace as per your requirement.


Step 2: Debug your code

After debugging open intellitrace window & click on Break All. Then you will get the IntelliTrace log as follows.


Step 3 :Select the Event you want to see the values

As you can see there is an exception in my code. So I will double click on that exception thrown event so that the trace will point me to the exact code location. There you can see there are set of tools available to step in & step back the method calls of your debugger session. which give you the faility of see the history debug data rather re-debugging the code.


You can save this save & share with anyone in you team as well.

Happy Debugging !!!!

No comments :

Post a Comment