Check-in policies in Team Foundation Server ensure that code checked into version control meets the defined quality requirements of your team. This policy pack wants to offer the anxious project leader a wide range of different policies to meet their typical needs.

LogSubstPol is a TFS check-in policy which insertes the check-in comments and other keywords into your source code, so you can keep track of the changes even if you are not connected to TFS. It can be compared with the $log$ (and other) substitition in any other CVS systems.

TFS Code Review Workflow This project is a combination of a Code Review Work Item and a Code Review Check-in Policy. The check-in policy doesn’t allow a check-in unless it has an associated Code Review work item, and that work item is set to approved. Only people in a TFS group named [Project]\Code Reviewers can set an item to approved. Workflow: 1. Dev finishes code and wants it reviewed so they shelve the changeset and create a Code Review work item and mention the name of the shelf set. This is assigned to a general Code Review team. 2. People on the code review team have event subscriptions which sends them an e-mail when a workitem is assigned to the Code Review group. One of them will open the work item, review the shelf set and resolve the item as 'Accepted' or 'Needs changes' which assigns it back to the original dev. 3. Once in an approved state the dev can check-in and associate to the work item which will close it.

It is best practice to get the latest version of your code before checking in. Currently, there is no way to enforce this. This is why I created a TFS Checkin Policy that ensures that developers are editing files based on their latest version.