Based in Sydney, Australia, Foundry is a blog by Rebecca Thao. Her posts explore modern architecture through photos and quotes by influential architects, engineers, and artists.

Solution: Using Source Server with Team System Source Control

If you just want to go to the site: Go here: http://SourceServer.Osherove.Com .
A team I work with needed Source Server usage support for Team System. Unfortunately, this is just about the only place online that really talks about source server besides the MSDN docs - until now.
Microsoft source server is part of the Debugging Tools For Windows package. It enables a client to retrieve the exact version of the source files that were used to build an application(while debugging!).
Because the source code for a module can change between versions and over the course of years, it is important to look at the source code as it existed when the version of the module in question was built.
The source server retrieves the appropriate files from source control. To use the source server, the application must have been source indexed
(for in depth info on Source Server read "srcsrv.doc" installed under the Source Server Install folder/SDK)
 
Support for various Source Control Systems
SourceServer comes with pre-made modules for Visual SourceSafe, Subversion and Perforce, but not for Team Foundation Source Control. This script adds Team System Source Control Support to Source Server.
 
 
Related files:
    * TF.pm : Perl script that integrates into Source Server and "talks" to TF.Exe (TF.Exe is part of team Foundation). Script was written by Michael Sheinker, a bright fellow from a project that I consulted to, who agreed to share it.
    * TFIndex.cmd : Simple command line to initiate PDB Indexing for Source Server on Team System Files

See you at Tech-Ed Europe!

Some updates about the desktop screenshot contest