Please refer to our library of tooling and guidance solutions for
pointers to new content on our
and MSDN/VS.com, such as:
- Blog posts:
- Alternative Branching Strategies
- Version Control Guidance – Frequently Asked Questions
- Walkthrough (Branching Strategies):
Part 1 – MAIN Only and Simplicity Rules,
Part 2 – Development Isolation,
Part 3 – Feature Isolation,
Part 4 – Release Isolation … audit alarm,
Part 5 – Servicing & Release Isolation
- Walkthrough (TFVC):
Part 1 – Create a new local workspace,
Part 2 – Use the local workspace in online mode,
Part 3 – Use the local workspace in offline mode,
Part 4 – Explore the diff and merge tools
- Git for the TFVC User – Workflows:
Part 1: Making Changes,
Part 2: Reviewing Changes (No Conflicts),
Part 3: Reviewing Changes (With Conflicts),
Part 4: Converting a TFVC repository
The purpose of this project is to build some insightful and practical guidance around branching and merging with Visual Studio Team Foundation Server by the Visual Studio ALM Rangers . The new guidance builds upon the previous release with some updates to
the core materials as well as guidance on additional scenarios that include guidance for sharing resources in Team Foundation Server via branching.
Branching and merging, dependency management and version control of software is a very large topic. It is an area where there is a lot of maturity in the software industry. This Ranger solution focuses on applied and practical examples that you can use right
now. The guide includes discussions around concepts and strategies but also focuses on practical Hands-on Labs (HOL) and walkthroughs.
With version 3 the team is introducing 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 focused on branching and merging scenarios, TFVC Gems and Dependency Management using NuGet, and Git for the TFVC User.
Visual Studio ALM Rangers
This guidance is created by the Rangers who have the mission to provide out of band solutions for missing features or guidance. This content was created with support from Microsoft Product Group, Microsoft Most Valued Professionals (MVPs) and technical specialists
from technology communities around the globe, giving you a real-world view from the field, where the technology has been tested and used.
- Bijan Javidi, Bill Heys, Bob Jacobs, Brian Minisi, Brian Randell, Clementino de Mendonca, Daniel Manson, James Pickell, Jens Suessmeyer, Lennart Jansson, Mathias Olausson, Matt Velloso, Micheal Learned, Neno Loje, Oliver Hilgers, Sin Min Lee, Taavi Koosaar,
Tony Whitter, Willy-Peter Schaub
- Anil Chandra Lingam, Bill Heys, Brian Minisi, Clementino de Mendonca, Daniel Manson, Jahangeer Mohammed, Jansson Lennart, Jelle Druyts, Jens Suessmeyer, Krithika Sambamoorthy, Matthew Mitrik, Michael Fourie, Micheal Learned, Neno Loje, Oliver Hilgers, Sin
Min Lee, Stefan Mieth, Taavi Koosaar, Tony Whitter, Willly-Peter Schaub
- 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, Stawinski Fabio, Taavi Kõosaar, Tina Botes, Tommy Sundling, Vinicius Hana, Willy-Peter Schaub
How to submit new ideas?
The recommended method is to simply post ideas to the community or to contact the Rangers at
Post comments on the