IntelliTrace

IntelliTrace is a feature of Visual studio Ultimate that enables application debugging using a historical execution log.
Course info
Rating
(101)
Level
Intermediate
Updated
Sep 27, 2012
Duration
5h 30m
Table of contents
IntelliTrace Introduction
IntelliTrace and Developer Specific Scenarios
Enable Testers to Capture IntelliTrace Logs
Using IntelliTrace in Production
IntelliTrace Under the Hood and Advanced Configuration
Description
Course info
Rating
(101)
Level
Intermediate
Updated
Sep 27, 2012
Duration
5h 30m
Description

IntelliTrace is a feature of Visual studio Ultimate that enables application debugging using a historical execution log. This course explores how to use IntelliTrace to enhance interactive debugging sessions, as well as how to leverage IntelliTrace as a postmortem debugger in testing environments (using the Microsoft Test Manager) and on production systems. Several advanced topics such as CLR profiler integration and collection plan tuning are also explored in depth.

About the author
About the author

Marcel is the co-founder and CTO of Xpirit, a high-end consulting firm based in Hilversum, Netherlands. Helping organizations transform towards a high speed, innovative, and productive organization is his passion.

More from the author
More courses by Marcel de Vries
Section Introduction Transcripts
Section Introduction Transcripts

Enable Testers to Capture IntelliTrace Logs
Marcel de Vries: Hi, welcome at this third module of the Pluralsight training on IntelliTrace. In this module we can focus on how we can configure Microsoft Test Manager to capture IntelliTrace log files while testers are testing your application. My name is Marcel de Vries. This module contains three main parts. First we will start off with manual testing with Microsoft Test Manager. Now we will give you a short description of what Microsoft Test Manager is. Now I want to make a disclaimer here that this is not a course on Microsoft Test Manager, so I will only cover the basics that are required for us to understand how we can configure Microsoft Test Manager so it will run IntelliTrace in the background and capture all the information that we need to actually debug with historical debugging. Next we will have a look at how a tester normally files a bug from Microsoft Test Manager. So we need to learn how a tester runs a test manually in Microsoft Test Manager, and how they can file a bug that contains all the diagnostics information that is necessary for us as a developer to do a good historical debugging session. Now this is meant to give you a fair understanding on how the flow between testers and developers will take place, and what the additional things are that testers might do to improve the IntelliTrace debug experience, so they can add meta data to the IntelliTrace file so that we spend less time finding the actual place that we need to start our debug session in. Now the last part will be how we can actually debug an IntelliTrace log file that comes from Microsoft Test Manager. We will see that it has some additional meta data that gives some clues on where we can best start our debugging session.

Using IntelliTrace in Production
Welcome to this fourth module of the Pluralsight training on IntelliTrace, my name is Marcel de Vries. This module will cover everything you need to know about capturing IntelliTrace log files from non-development environments. This is called, by Microsoft, capturing log files in production. In this module, I will walk you through how you can download and extract the IntelliTrace collector for Visual Studio 2012. I will show you what is in the package, and what the main scenario's are for which you can use the package that you downloaded. So the two scenario's for capturing IntelliTrace log files in production environment as Microsoft calls them, is capturing IntelliTrace log files from a standalone application, like the tip calculator that we've seen in the previous modules, and the other scenario is capturing IntelliTrace log file for web application on a web server. Now, once we have known how we can capture those log files, I will show you the debug experience that you have, within Visual Studio 2012. There's a different experience for the stand alone IntelliTrace collections, and web applications, because Microsoft added some additional features to the IntelliTrace log files that are captured from a web application, that includes, for example, the page request that came in, and so you can correlate them to, for example, exceptions that you will find in your IntelliTrace log files. Now, one thing to note is that capturing log files is available for everybody without any licenses, but for debugging the actual log files that you've captured, you need Visual Studio 2012 Ultimate edition.