Demystifying Debugging with Visual Studio Ultimate and Intellitrace

www.teamsystemrocks.com
@mickey_gousset
Live messenger:mickey_gousset@hotmail.com
2010 Debugging Features
Breakpoint Labeling
    This is useful for when you have multiple breakpoints, set the labels, After setting then you can group and search on them to enable/disable them
Import/Export Breakpoints
    Allows multiple users have same breakpoints (save line numbers so code must match)
Hit Count
    Allows you to set when it breaks on...nice for when in loops
    Will add a + to red dot to indicate it has a condition for it to go off
Can Drag Data tips and look at last value when done
IntelliTrace
Helps eliminate the no repro scenario
capture debugger state information during program execution
It collects 3 types information,Intellitrace Events, Method/Entry Calls, Breakpoints
THere ae about 150 different events you can trace
Tools->OPtions->Intellitrace to see if turned on

Should open intellitrace window to see intellitrace data
If you want to see local variables, set debugger lines and it will capture what local variables were when it hit debugger line
Can turn on calls view in options...then you see calls and navigate through the calls using left bar of your code
Warning turning this on could slow down running
all the info is saved in a log file you can look at
  you can set size of it under options
  If you close VS it will delete all intellitrace files you have so if wish to keep, move it before closing VS
  Click on exception and open up VS to where exception occurs even if you dont have solution open
  (must have pdb file and it must be from the build)
Intellitrace and testers
Do a build
tester runs thier test case
Tester files a bug with attached Intellitrace
Programmer can look though intellitrace log
Tester can set in Test Manager what kind of intellitrace datta they want to capture
Saving a bug in Test manager save lots of inforation that deveoper can use uncluding an intellitrace log
in the build definition, under process tab. there is a source and symbols setting...set index sources to true...give it a path to a share (place to store pdb files)
Create share to save pdbs and add file to build defifinion
And Source serving indexing -modifies info in PDB to include
  Source control provider info
  Command line to retrieve file (tf.exe)
  intellitrace lets you fix bugs w/o having to retrace tester steps
Creating Custom Intillrtace events
Warning not supported by MS
No official documentation
need to hack CollectionPlan.xml