Branch to share assemblies and other blobs between team projects?

Mar 19, 2013 at 7:22 PM
Is branching a good or even the best way to share assemblies, libraries and other blob assets between different team projects?

I don't recall seeing this use case covered in the ranger guide.

There is an option that is not super well documented:
  • Immediately convert source folder to branch (enabled visualizations)
It is the default but I'm not sure if it is relevant for blob assets.
Mar 20, 2013 at 5:58 PM
Hi John,

Take a look at the "Advanced Version Control Guide" document. There is a section titled "Dependency Management Patterns". It goes through different scenarios of sharing source code, binaries, and 3rd party libraries.

Branching vs Not branching comes down to how often the libraries and blob assets change. If they don't change that often, you may just want to create a folder for each version and reference or update them when needed. You need to create a dedicated team project for you shared assets.

Let me know if you need more info.

Cheers,
Ahmed
Developer
Mar 21, 2013 at 7:45 PM
Hey all,

This is a huge topic area, take a look at the guide for pros/cons. However also take a look at NuGet and NuGet package restore as a potential solution for dependency management which can in fact get you away from putting binaries in the tree to begin with.