Best practices for multiple projects?

jessek · Post by **jessek** » Thu Mar 01, 2007 10:28 am

I'm making the move from a single-developer environment to a larger team, and I'm trying to figure out how to set up my repositories -- any help would be much appreciated!

I'm using the current version of Vault, with VS 2005 integration.

The questions are:

- one repository for everything, or several? can you have more than one project in a repository? more than one solution? should you?

- if not everything is in the same repository and/or solution, how do I deal with references? Right now, it's a big mess.

Here's what I have:

A VB.NET class library "utils_1.dll"

A VB.NET class library, "utils_2.dll"

3 websites. All reference utils_1.dll, one references utils_2.dll. (There's a Web Deployment Project for each of these -- but this only needs to exist on the machine that's doing the final builds.)

2 windows applications. Both reference utils_1.dll, one references utils_2.dll

Both the websites and the applications reference some of the Microsoft Data-Access Application Block dll's. (I don't have the source code for these; binaries only.)

What's the best way to set this all up so that we're not wrestling with the references?

Thanks in advance...

lbauer · Post by **lbauer** » Thu Mar 01, 2007 11:01 am

You can have more than one project per repository. If you are sharing or re-using dependent files and references in different projects, they should be in the same repository, since you can't interact across repositories.

Details here:
http://support.sourcegear.com/viewtopic.php?p=5183

jessek · Post by **jessek** » Thu Mar 01, 2007 1:17 pm

Thanks, Linda. So it sounds like it's 50/50 -- you suggested keeping everything in one repository, and the article you linked to makes some good arguments for using multiple repositories.

Can I have multiple VS solutions in one repository? AFAIK, I can't have both windows forms apps and web applications in the same solution.

lbauer · Post by **lbauer** » Thu Mar 01, 2007 1:43 pm

Yes, you can have more than one VS solution in a repository.

My suggestion was to use the same repository for projects that are sharing the same files or other resources.

If every project stands alone, then you can use a repository for each project. You can put multiple projects in one repository. What you don't want to do is put different parts of a project in different repositories.

futura · Post by **futura** » Tue Nov 06, 2007 10:37 am

In the 4.x version of the Vault can one bind multiple projects within a solution to multiple repositories?

I've searched through here and found no definitive answer, and don't see it on the latest fix list. I was hoping the new VS.NET 2005 client may address this issue, however.

In our scenario, we have database projects, .NET code, and SQL Reporting, etc. in different repositories. We like to have our .NET project code as various projects within a solution, and then have the associated database projects also in the solution. However, because of the issue of going across repositories we haven't been able to do this since we went to Vault.

As we're considering upgrading from 3.x to 4.x it'd be useful to know what the status of this is.

Thank you,
Aaron

lbauer · Post by **lbauer** » Wed Nov 07, 2007 7:18 am

Vault 4.0 does not support having a solution with projects bound to multiple repositories.

futura · Post by **futura** » Thu Nov 08, 2007 8:29 am

lbauer wrote:Vault 4.0 does not support having a solution with projects bound to multiple repositories.

Do you know if this is a planned feature enhancement in the 4.x range of versions or never being planned?

SourceGear Support

Best practices for multiple projects?

Best practices for multiple projects?

Multiple solutions in one repository?

Binding one solution to multiple repositories.