Organizational question

CityOfOrlando · Post by **CityOfOrlando** » Tue Aug 08, 2006 11:54 am

We are a small shop, fewer than 10 .NET developers. We are transitioning from one developer/one application to multiple developers working on an application. We just got SourceGear Vault 3.5 setup and we are looking to organize in the best possible way up front.

We're leaning toward one repository for each solution, this seems to be a more natural way of organizing our code. However, we have a number of in house reusable assemblies that are used across solutions. We typically would use project references for these assemblies (rather than file references). A project could therefore be part of multiple solutions.

Is this something we can accomplish in SourceGear? Should we organize differently? Should we switch to file references?

Any comments and/or thoughts are appreciated.

William Kunneke

Beth · Post by **Beth** » Tue Aug 08, 2006 3:18 pm

Eric Sink has written about the organization of repositories at this link: http://www.ericsink.com/scm/scm_repositories.html

We also have some forum postings with more information:
http://support.sourcegear.com/viewtopic.php?t=49
http://support.sourcegear.com/viewtopic.php?t=193

ian_sg · Post by **ian_sg** » Tue Aug 08, 2006 5:01 pm

I'll add that there's no good way to share code between repositories. You can't branch or share across repositories, you can only copy/move via the import/export tool shipped with 3.5.

Given that you know you need to share code among your projects, one repository per solution would definitely be less than ideal.

CityOfOrlando · Post by **CityOfOrlando** » Wed Aug 09, 2006 9:01 am

Thanks for the input, this was exactly the kind of information I was looking for. I started to look through Eric's website yesterday, but hadn't gotten to chapter 4 yet. Chapter 4 appears to answer all my questions.