This project has moved and is read-only. For the latest updates, please go here.

Request: Branching Guidance using Feature Builder

Aug 9, 2010 at 6:40 PM

My developers/team has a really hard time understanding branching and merging and no matter how many times I print out the branching guidance document/diagrams (which are indeed pretty) my developers keep saying that branching is hard, using labels with branching is complicated, and using the branch visualizations/track changeset doesn't make sense. I've been working with them on our branching structure and at times I too seem to get lost in the features....and don't fully remember the WHY behind what we're doing in the tool. A quick re-reading of the guidance helps...but it sure would be nice to have a practical example that my developers can have in their visual studio environment.

If you guys could create a Feature Builder lab that would be great. Heck even starting from the Create Team Project step all the way through to merge resolution would be even better.

And possibly could you explain why you would use the create branch from existing source control option in the Team Project creation wizard...that'd be nice as well.

Thanks for the guidance so's saved our bacon more than once....just hoping to see even more practical training on TFS 2010. 

Aug 19, 2010 at 3:50 AM

Is this idea under any consideration to be added to the next release of the guidance?

Aug 19, 2010 at 11:46 AM
Edited Aug 19, 2010 at 7:58 PM


With respect to to providing guidance and / or a HOL using Feature Builder, I would say that we would consider any delivery modes or formats that will improve the communities ability to consume and beneft from the guidance. I cannot, however, commit to any specific format without discussing this with the leadership of the VS ALM Rangers program. One of the goals, when we undertake a Ranger project, is to make it easy for people to contribute. We have found the Word format (with PDF and XPS options) to be a reasonable publishing format for codeplex. I am continuing to look at alternative (additional) formats such as Feature Builder and Compiled Help (CHM) files.

With respect to a suggestion for a lab, the existing guidance contains a downloadable lab and sample files that has been well received. It can be used with any VS TFS 2010 environment (physical or virtual).

I will respond to the rest of your question shortly.

Bill Heys
VS ALM Ranger

Aug 30, 2010 at 4:35 PM


        While I can understand that you can't commit to any specific format without first discussing it with the leadership and the VS ALM Rangers would be nice to see into the process and learn about what in fact is going to be worked on for the next release via the workitems that could be created here on codeplex.

Thanks again for your efforts on this really is good....just hoping to see it continue to be developed and improved over time.