Version Control guidance v3.BETA flight has landed

We are pleased to announce that the v3 BETA has of the Version Control (ex Branching and Merging) Guide has shipped.

Update 2014-05-14: See Delving into the new Version Control Guidance … what’s changed (1) and where is Git if you are looking for news on the Git for TFVC User eBook.

what’s new?

Third version of this blockbuster guidance has been split into separate topics as summarized below, allowing you to pick the “world” (guide) you are interested in. This release delivers a new crisper, more compact style, which is easier to consume on multiple devices without sacrificing any content. The content is updated and aligns with the latest Visual Studio technologies and incorporates feedback from the readers of the previous guidance.


Branching Strategies
Practical guidance on a number of (not all) common Branching Strategies and usage thereof.

  • Branching concepts
  • Branching strategies
  • Walkthroughs


Team Foundation Version Control (TFVC)
Practical guidance on how to use Team Foundation Version Control (TFVC) features.

  • Workspaces
  • Merging
  • New features, i.e. Code Lens
  • Walkthroughs

Dependency Management with NuGet
Practical guidance on dependency management, using NuGet with Visual Studio.

  • Managing shared resources
  • Dependency management
  • Walkthroughs

where’s the stuff?


why BETA?

The guides are feature and content complete, technically reviewed and therefore consumable as a BETA. To reach the RTM quality bar we are missing the final copy edit.

what’s cooking?

  • The Using Feature Toggles as an Alternative to Development or Feature Branches article, by Bill Heys, references by the Branching Scenarios guide is expected to appear in the MSDN Magazine shortly. Watch this space!
  • The Git for TFVC user guide is still under development and not included in v3.BETA.

the team

A special THANK YOU to the team of ALM Rangers who volunteered their personal time and contributed their real-world experience to deliver this solution: Alan Wills , Andy Lewis, Anna Galaeva, Bill Heys, Dan Hellem, Esteban Garcia, Gordon Beeming , Hamid Shahid, James Waletzky, Krithika Sambamoorthy, Larry Brader, Malcolm Hyson, Matt Mitrik, Michael Fourie, Micheal Learned , Michel Perfetti, Peter Provost, Robert MacLean, Fabio Stawinski, Taavi Koosaar, Tina Botes, Tommy Sundling, Vinicius Hana, Willy-Peter Schaub.

Did I forget anyone? If yes, please ping me with a bang (!)

please send candid feedback!

We can’t wait to hear from you, and learn more about your experience using the add-in. Here are some ways to connect with us:

  • Add a comment below.
  • Ask a question on the respective CodePlex discussion forum.
  • Contact me on my blog.
Comments (2)

  1. Anna Galaeva says:

    Working on this ALM Rangers guidance was extremely rewarding, because it covers on of the fundamental areas, which affects pretty much everybody on project teams. It  can be efficiency booster, if done right, or source of dissatisfaction, delays in process and source of confusion, if done wrong. This guidance share best practices and provides practical explanation on WHY teams should do things one way or another, and of course covers HOW aspect. It was great to be reviewer for that project – I learned many new things myself.

  2. EstebanFG says:

    I really enjoyed working on the Version Control guide because I was able to work with an extremely passionate and smart team on guidance that can benefit so many developers out there.  My first exposure to any Rangers project was the original Branching Guide a few years ago so it was a very big deal for me to be able to work in a project related to it.  This type of guidance can greatly enhance your team's abaility to manage and deliver software.

Skip to main content