Ann: Branching Tool for VS2005 solutions (with source)

Ward Bekker · Post by **Ward Bekker** » Tue Apr 24, 2007 3:11 am

Hello,

I've created a Vault branching tool for VS2005 solutions using the Vault Client API.

More information can be found on my blog

Feedback is most welcome.

To Sourcegear: I've included your Vault api dll's in the zip file. Is that OK?

Post by **jclausius** » Thu Apr 26, 2007 9:02 am

Although this goes against our licensing policy, we'll make an exception. You have permission to redistribute the compiled binary DLLs for the Vault Client API.

Note, including the DLLs in your .zip file limits the branch application to a specific version of the Vault client.

Ward Bekker · Post by **Ward Bekker** » Fri Apr 27, 2007 12:23 am

jclausius,

Thanks!

I'll exclude them from the zip file then and point out in the docs you need to fetch the api files for your specific version. I needed to update them any how because of some minor modifications.

Also, you might want to add a licence.txt file to your API distribution files, as the readme of my version does not say anything about the licence under which the files are made available.

Bye,

Ward

Ward Bekker · Post by **Ward Bekker** » Fri Apr 27, 2007 1:52 am

I uploaded a new version without Client API files for a specific version and some small updates.

Documentation & Changes

The sources

frizzo · Post by **frizzo** » Fri Apr 27, 2007 10:19 am

That is awesome. Our branch contains our entire suite of apps and over 200 files with bindings. Unfortunately they are a mix of VB6, VS2003 and VS2005 solutions.

Does your app work with VS2003 projects/solutions?
Does it also fix the MSSCCPRJ.SCC bindings?

Ward Bekker · Post by **Ward Bekker** » Sun Apr 29, 2007 3:47 am

Hi Frizzo,

Currently it's working for VS2005 solutions with a single solution file and multiple project files (including setup projects). It also fixes the MSSCCPRJ.SCC for all projects.

You can add VS2003 support yourself. Look at the ReplaceInSolutionFile method BranchCreator.cs, you will see that for the .SLN file it's a simple find and replace of the root vault binding path. I think for VS2003 solution it will be similar. If you need help, you can find my e-mail in the docs. If you have VS2003 working send me the code and I'll update the original zip.