Showing posts with label TFS Source Control. Show all posts
Showing posts with label TFS Source Control. Show all posts

Thursday, April 05, 2007

Deleting Team Builds ...

Been trying to remove some Testing Build Types that I created while playing with Team Build and got really lost, so I thought it might be helpful for playing geeks like me :)

Actually it's very easy ... All you have to do is go to Source Control Explorer, Get latest from the TeamBuildsTypes Project, remove those Builds you no longer need, and then Check in them back again ... Voila :)

Same applies to Editing Team Build types ... you have to check them out first ...

Hope that was helpful ...

Wednesday, March 21, 2007

TFS Branching Guidance ...

TFS Branching Guidance is now available on CodePlex

The purpose of this project is to build some insightful and practical guidance around doing branching and merging using Team Foundation Server. It's a collaborative effort between industry experts, Microsoft Services, patterns & practices, and VSTS team members.

Monday, March 05, 2007

TFS Migration Toolkit Specs Published

If you are interested in writing version control or work item tracking conversion tools, be sure to check it out the TFS Migration Toolkit Specs that has been just published and give them your feedback.

Thursday, November 09, 2006

TFS VC Check-In Policies

A Check-In Policies pack will be available soon containing the following:
  • Check-in policy granularity
    It will be based on the one available in Code Gallery, the changes will be mainly packaging it, changing some of the UI and taking out some of the complexity.
  • Work-Item Associations
    It will be based on specified queries to check the associated work items by the developers are part of the queries or else it will be blocked, that will help making sure all check-ins are associated with real work.
  • Banned files
    This policy allows you to specify a file extension or a regular expression in order to keep files that you don’t want out of version control. This is usually used for dll’s, build artifacts, or some website files that are automatically generated.
  • Check-in Comments
    This policy gets shipped as part of the SDK. It looks at the check-in comments and makes sure it is not blank.