Referencing a Project in a different repository

[jsummers]

Hi Everyone,

I've been using SourceGear products for a while now and I must say I'm very impressed!

However, there is one problem that has come up.
We have a repository which contains all of our in-house tools, utilities and common components, some of which are used in projects in other repositories.
I understand that I cannot branch between repositories, I knew this before starting to use Vault. What I need is some direction on how to reference our common components without having an ugly 'Dependencies' folder with a load of binaries in for each project

I've been racking my brains over this for a week, so any help would be greatly appreciated.

Regards,
Jason

[Beth]

As I see it, there are two options:
1) Pull down your dependencies first, but don't have them bound to source control. Then your project would just reference them on disk. If you needed to check them out, you would have to do that with the Vault GUI client.

or

2) Make a dependencies folder in each repository and only put in the latest version of the dependency that you need. Any actually code changes to the dependencies would still happen in the repository where all the code for those items resides. If you need to update the dependency you could check it out, perform a Get from the repository where the update resides to the working folder where you checked out the item and check it in.