Vault 3.0.6 - Branching and Visual Studio 2005

Predjudice · Post by **Predjudice** » Wed Apr 23, 2008 3:27 am

My company's solution currently has 50+ seperate projects in a single solution, all contained in Valult and worked on primarily using Visual Studio 2005 with the Vault source control plugin. We've just started to implement branching and though we've had no problems creating the branch in Vault, there doesn't seem to be an easy way to re-bind the Visual Studio Solution and projects to the new branch without modifying the source control bindings for each project seperately.

Is there a tool available which can re-bind all the projects as part of a branching operation?

Beth · Post by **Beth** » Thu Apr 24, 2008 9:50 am

There isn't currently, but that's a good idea. I'll put in a feature request.

You're on Vault 3.0.6? You might want to look into going to 3.1.9 since the 2.0 .NET framework and VS 2005 is support with that version. I can't guarantee what kind of results you'll get with 3.0.6.

Beth · Post by **Beth** » Thu Apr 24, 2008 9:52 am

50+ seperate projects in a single solution

Oh, and you should just be able to perform the unbind and rebind of the entire thing at once. Open the solution, unbind, click ok and save it to disk that way. then go in and rebind either all at once (if the layout in Vault matches what's on disk), or each one, and click ok only after all 50 are rebound.

Predjudice · Post by **Predjudice** » Fri Apr 25, 2008 4:43 am

The gripe is that it takes a lot of effort to re-bind all those projects by hand on the semi-regular creation of a branch and the subsequence merge into the trunk.

We currently don't have any problems with Vault as such, just this issue which makes branching vastly more time-consuming than it ought to be.

Post by **jeremy_sg** » Fri Apr 25, 2008 3:42 pm

We agree that this is a chore. That's why we designed the 4.1 Enhanced Client to handle branches without needing to be rebound.