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...

Microsoft source server Source Server is coolness. If you don't want to read further - This script adds Team System Source Control Support to Source Server. Microsoft source server is part of the Debugging Tools For Windows package. It enables a client to retrieve the exact version of the source...

If you just want to go to the site: Go here: http://SourceServer.Osherove.Com 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...

To Skip this Intro, read the full article here: A Simple Version Control Strategy Using Team System I was recently asked by a client who I'm helping to integrate Team System, to create a strategy for the organization and future projects for managing multiple versions of applications and code - A version...

To Skip this Intro, read the full article here: A Simple Version Control Strategy Using Team System I was recently asked by a client who I'm helping to integrate Team System, to create a strategy for the organization and future projects for managing multiple versions of applications and code - A version...

Parts of this article are compiled from http://msdn.microsoft.com/library/en-us/dnvs05/html/vs05teamsys.asp?frame=true Update : Added questions about sstoring third party components, sharing project output internally and branching compared to Subversion. I was recently asked by a client who I'm helping...

In case you were wondering, I'm still alive and posting (although not as prolifically as my good friend Noah ). I've been up to a few cool things - here is a status update: Professional Team Foundation Server : I got word that my first book Professional Visual Studio 2005 Team System is a great...

Posted at Ardent Dev by Derek Hatchard ( Go directly to post ): I believe strongly that you need great tools to support a great development process. There are a few core tools every team should have: work item / defect tracking system, automated build system, developer testing tools (including unit testing...

Check out this article by Nigel Cheshire - quoting both Sam Guckenheimer and Joel Spolsky about whether or not measuring developer performance is a good thing or not. Both Sam and Joel say to stay clear away from doing this. Where do you stand? Personally, I say that we need to "professionalize"...

Oren pointed out that he would run away from TFS because it’s a “zero friction tool”. He does have some valid points, mostly about the length of time some of the source control actions might take, though personally I haven’t found this to be much of a problem. I'd usually say "stay clear of all-or-nothing...