Team Development with Visual Studio Team Foundation Server

long as the revision does not conflict with a change that is already pending in your
workspace.
5. Optionally, you can clear the Restore work items and check-in notes option if you
do not want to have the work items and check-in notes associated with the shelveset
restored. When the Details dialog box appears, select the shelveset or shelveset items
you want to unshelve into your workspace, and then click Unshelve.
Additional Resources
• For more information, see “How to: Shelve and Unshelve Pending Changes” at
http://msdn2.microsoft.com/en-us/library/ms181404(VS.80).aspx
Resolve One Work Item per Check-in
After resolving a work item, check in your pending changes and update the work item
status. This practice serves the following purposes:
• It provides a consistent record in the source control database that can be used to
review changes per work item, or to back a work item out if necessary in the future.
• It ensures that you do not wait too long between check-ins. The longer you wait
between check-ins, the more likely that you will have a conflict that requires a
manual merge and additional testing.
Additional Resources
• For more information about check-ins, see “How to: Check In Pending Changes” at
http://msdn2.microsoft.com/en-us/library/ms181411(VS.80).aspx
• For more information about work items and changesets, see “How to: Associate
Work Items with Changesets” at http://msdn2.microsoft.com/enus/library/ms181410(VS.80).aspx
• For more information about reviewing work item details, see “How to: View Work
Item Details from Pending Changes Window” at http://msdn2.microsoft.com/enus/library/ms245467(VS.80).aspx
Use Check-in Policies to Enforce Coding Standards
Use check-in policies to enforce coding standards across your development team. Checkin
policies help to ensure that all source code checked into TFS source control meets your
defined coding standards.
The code analysis check-in policies that ship with TFS enables you to ensure that static
code analysis has been run on code before it is checked in. You can fine-tune the code
analysis policy to check many different rules. For example, you can check rules
governing design, interoperability, maintainability, mobility, naming conventions,
reliability, and more.
To enforce a code analysis check-in policy for a team project
1. In Team Explorer, right-click your team project, point to Team Project Settings, and
then click Source Control.