What you should know about Version Control in TFS 2010
- Posted: Apr 24, 2011 at 6:00 AM
- 5,873 Views
Right click “Save as…”
This is a recording of an MSDN Live Meeting held on February 15, 2011 at Microsoft in Belgium.
Unlike Visual SourceSafe (VSS), which relied on a file-based storage mechanism, Team Foundation version control stores all artefacts, as well as a record of all changes and current check-outs in a SQL Server database which makes it highly reliable and scalable. It supports features such as multiple simultaneous check-outs, conflict resolution, shelving and unshelving, branching and merging, and the ability to set security levels on any level of a source tree, alongside the most visible features of document versioning, locking, rollback, and atomic commits. The source control mechanism integrates with TFS Work Item Management as well. TFS administrators can enforce check-in policies that require specific requirements to have passed and individual versions of files can be assigned labels. This session is targeted towards developers who want to know all the details about the new version control features in Team Foundation Server 2010.
Pieter Gheysens is the founder of Sparkles (www.sparkles.be) and focuses as a Visual Studio ALM MVP and Certified Scrum Master on Application Lifecycle Management solutions for the Microsoft .NET Development Platform based on Team Foundation Server. During the last 10 years, Pieter has been involved in many large enterprise development projects as a developer, team lead and software architect. He's passionate about setting up the optimal team development environment to deliver high quality software and strives to get the best out of people, tools and processes. You can read about his experiences at intovsts.net. Since a few years now, Pieter is the User Group Lead for the Belgian Visual Studio User Group (www.visug.be) which organizes many free technical community events with local and international speakers.