Shared Projects Best Practice

Evo · Post by **Evo** » Thu Oct 06, 2005 8:54 am

Hi. I recently downloaded Vault and I believe we will be making it our corporate standard. I LOVE IT!

Here is a question that I am sure comes up repeatedly, but I have not found any specific posts using the search function. (No flaming.)

Our organization has several libraries which are single .NET or COM projects. These projects are used in several large solutions containing multiple projects e.g.

Application
- BLL
- DAL
- UI
- Shared Library 1
- Shared Library 2

What is the best way of organizing my source tree so that each solution contains a reference to the shared project, but not a separate copy.

Are shared folders the best way of doing this or do you guys recommend another approach? What I was thinking is something along the lines of

$
- SharedLibrary1 (Shared)
- SharedLibrary2 (Shared)
- Application1Solution
--- BLL
--- DAL
--- UI
--- SharedLibrary1 (from Share)
- Application2Solution
--- BLL
--- DAL
--- UI
--- SharedLibrary1 (from Share)
--- SharedLibrary2 (from Share)

dan · Post by **dan** » Thu Oct 06, 2005 9:02 am

What you've described is what we would recommend - all projects within a solution need to be underneath the solution, so the best way to do that is to share the common library into each project that needs it.