Code Coverage, Source Control Tips, and Grok Talks
VSTS Quality Tools -
Running Tests with Code Coverage
David Williamson and Dominic Hopton do a great job of presenting the three common ways that people will probably use VSTS to collect data, in this case, specifically code coverage data.
Scenario 1 will probably the one that I use the most, as I am a small shop, and therefore play the role of both developer and tester, which gives me access to the source code.
And yes, I am a big fan of using VSTS in a small shop. Ask me if you want to know more.
Adam Singer - Extra! Extra! Get the latest news!
Adam provides some nifty Source Control Tips. I especially like the use of "~":
Another nice shortcut is the tilde syntax to specify versions of an item. Suppose you want to compare the version of Progran.cs from changeset 10 with the version from changeset 15. You could write "h diff Program.cs;C10 Program.cs;C15". However, you could also take a shortcut and use "h diff Program.cs;C10~C15".
For those that don't know, "h.exe" is the command-line utility for checking in and checking out stuff, among other things.
Grok Talks
There were great 10 minute or less presentations done by different Regional Directors at Tech Ed. This was a very cool idea, and I think it worked well. The following talk is Team System related:
Mitch Ruebush - Extending Visual Studio Team System
I've never used InfoPath, but it looks like it will come in handy when modifying process templates. Another thing to put on my list.