One really great feature in Visual Studio Team System 2010 is IntelliTrace. IntelliTrace captures the current state of the debugger at multiple points during a program’s execution and, when F5 debugging, allows you to debug back in time to previous debug states in your program. This in and of itself is a very handy feature, but in this day and age it’s often hard to have a bug with an easy and consistent repro that you can debug on a local dev box.
The solution to this lack of a local repro is that not only does IntelliTrace enhance your local debugging experience, but it also saves all the collected debugger data points into a trace log file (.itrace extension) that can then be opened and debugged using Visual Studio later and on a different machine. An iTrace files allows a developer to debug in and around the point of failure after the fact.
Ian Huff wrote a very interesting article explaining every little detail about these iTrace files. Check it out!