Correct Branch Process

[jchannon]

I have an issue with "branching" using Vault. Lets say I have a solution with 25 projects in it. I need to branch one project.

As far as I see it I also have to branch the solution file (*.sln) as well so it knows to load the branched project.

Is that the workflow you would expect?

[Beth]

You only need one project branched, but you need to use it in the context of the entire solution were using it in before as well?

If that's correct, you could create a share at the solution level, and then just branch the .sln file and the project, since those are the pieces that will need to be changing.

[jchannon]

What is a Share?

This is just a simple example but the way I see SourceGear works is just taking a copy of the folder/files which is a bit messy really. Is there no alternative?

[Beth]

A share makes a copy, but what changes on one side also changes on the other. It would allow you to have a copy of all your other projects with the branched project that is going in a new direction. You don't have to go that route. It just sounded like an easy solution.

You could just branch the project and branch the solution file.

You could also branch the project and create a brand new solution file that makes use of the branched project and add that to Vault. If it has to reference the other projects to, then after the solution is added to Vault you can tie in the other projects.