Tfs Community Branch Tool


The Tfs Community Branch Tool Visual Studio Extension is based on the ALM Rangers Quick Respons Sample ALM Rangers Branch Tool vs extension. The goal is to provide a tool to automate branching task in the ALM Rangers branching guidance

(6) Review
Visual Studio
Download (2,426)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (6)
Q and A (4)
Sign in to write a review
Sort by:

by Gregorio de Almeida Prado Neto | October 22 2014

Looking forward for the update to Visual Studio 2013

Mattias Sköld October 28 2014
| Edit |

Hi, and thank you for the review.
Just wanted to let you know that I finaly got a VS2013 Beta 1 out of the door! Enjoy :)


by Sergio Peralta | October 14 2014

Good tool! But now I'm using VS2013 and this tool doesn't support it. There will be a future release that supports VS2013 ?

Mattias Sköld October 28 2014
| Edit |

A polite ping, to thank you for your review and let you know there is a Beta 1 for VS 2013 ...



by Thuc V Nguyen | November 08 2013

Great tool!!!
However it does not suppport Visual Studio 2013 thus I just got the source code at and compiled for Visual Studio 2013.

Mattias Sköld October 28 2014
| Edit |

It took a while, but now I have a Beta 1 for VS 2013!

by Sean Mackey | June 22 2013


by Clemens Reijnen (live) | May 12 2013

used it ... works great

by Willy-P. Schaub | March 30 2013

Thank you for driving this great productivity tool in the community!

Sign in to start a discussion

  • Cannot install on VS2013
    1 Posts | Last post June 25, 2015
    • Hello! I tried to install the extension on VS2013 and I have this error log:
      6/25/2015 11:16:13 AM - Searching for applicable products...
      6/25/2015 11:16:17 AM - Found installed product - Microsoft Visual Studio 2010 Shell - Integrated Mode
      6/25/2015 11:16:17 AM - Found installed product - Microsoft Visual Studio Professional 2013
      6/25/2015 11:16:17 AM - Found installed product - Microsoft Visual Studio 2013 Shell (Integrated)
      6/25/2015 11:16:17 AM - Found installed product - Global Location
      6/25/2015 11:16:17 AM - Found installed product - ssms
      6/25/2015 11:16:17 AM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
         at VSIXInstaller.App.InitializeInstall()
         at System.Threading.Tasks.Task.InnerInvoke()
         at System.Threading.Tasks.Task.Execute()
  • I don't understand the usage of this tool
    2 Posts | Last post October 27, 2013
    • (cross posted here:
      Hello guys,
      I'm evaluating tools that helps to manage branch for my team. We are working on a commercial product, so the tools must be chosen carefully to handle multiple releases, potential hotfix on older versions, etc.
      Basically, what I want is to reach what git-flow  allows.
      But because we are already using TFS (2012 today, but 2013 upgrade in the pipe) with Visual Studio 2012 (but we didn't use branches before), I'd like to "stick" to a full MS product line.
      Then I was looking for guidance, and I found this software. I've seen the short webcast Quick tour of the TFS Branch Tool VS Extension  on channel9 that demonstrate the tool. But it only covers the creation of the initial structure. What about day to day work?
      Let's say I've finished working on a feature or a hotfix. How can I guide the developer to merge to the correct branch? How can I have a easy to read view of the work?
      The tools said "automate branching task in the ALM Rangers branching guidance"... but I don't see any menu that can do that. The only thing I see is the "Create initial structure" menu.
      Did I miss something? Is there any other resource that can help me?
      I like GIT... I believe in its strong branching features. But I feel the git experience in VS 2012 is terrible... so I'd like to give a chance to TFS.
      As my team (including me) is not mature in managing branching, I must keep things as easy as possible, so any advise is welcome.
      thanks in advance
    • Hi Steve and sorry for the late reply...
      If you’re looking for guidance around TFVC branching, you should check out the ALM RAngers Branching Guide
      If you want a tool to help support and guide your team to automate TFVC branching tasks, you are probably on the right page, or at least Im not aware of any other tool to try to do the same. 
      The VISION for the BranchTool is to provide an experience like GIT Flow, but for TFVC. The sad truth is that we’re not there yet, but the Branching Tool is a good platform to start with. The reasons for it is that its basically driven by files called .branchplan. The idea is that we can add additional .branchplans for activities like finish a feature. If you create additional branchplans they will automatically get picked up by the tool and display inside the tool. 
      I’ve raised an Idea to integrate the branch tool and the branching guidance further on uservocie, suggesting that we should cover all activities in the branching guide with .branchplans file (and improve the branch tool) so you can have an experience like git flow. But at the moment this is what we got to offer.
  • Call from an Event Handler
    2 Posts | Last post May 15, 2013
    • A client would like to automate the branching structure at the point of creating new team projects.  This can be done by subscribing to the ProjectCreatedEvent.  Is there a way that this tool can be called from within this subscriber rather than having to code it?
    • You could probably use the code straight away, or consider just executing the command line util and wait for it to finish before continuing.
      I would personally not implement it in a event handler for the ProjectCreatedEvent, but rather look at owning the process and create the project with tfpt. I got some very old post on how to do it 
  • Copying files
    3 Posts | Last post April 15, 2013
    • Is there a built in action for being able to include files within the branch plan? When we create our base branching structure, we a have a couple of template files that need to also be checked in. It would be really great if we could include these with this tool as well when we create our own branch plan.
    • No, not out of the box so far, but I add it to the backlog :)
      The framework is really extensible, so it wouldn’t be so hard to do , I’ll see if I can find the time to squeeze in a blog post about it.   
    • That would be great. Thanks.