This project is read-only.

How to manage project dependencies

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

In general you should avoid dependencies that cross team projects and try to have all the related/dependent solutions/projects under same team project. This reduces the need for build script customization. If you have a dependency, use project references to define it. You should avoid file references as they are more difficult to manage. Note that project to project references are supported within a solution. Also a project file (csproj, vjsproj, vcproj, vbproj, etc) can be included by multiple solutions (sln files). Therefore, a project can be shared by multiple separate solutions.

Last edited Mar 26, 2007 at 11:21 PM by prashantbansode, version 3


lvildosola Mar 4, 2007 at 11:58 PM 
In Team Foundation Source Control you can share projects and still have them associated to a single source control reference. To do this make sure you add the project references in your Solution by using the "Add Project from Source Control..." option under the "File / Source Control" top level menu. Making the association this way allows to still manage modifications via Source Control independent of the Solution that references the project. That is, changes made in any one Solution that references a Project will affect all Solutions.