Guidelines on structuring solutions and projects in team build
- Single solution is best for small size projects.
- The most scalable and efficient way for managing and building large applications is team build is to have multiple independent solutions.
- Always avoid solution to solution references. They are not supported in Whidbey.
- Editing “Microsoft.TeamFoundation.Build.targets” file is (strongly) not recommended.
- Project to project references are supported within the solution. Moreover a project file (csproj, vjsproj, vcproj, vbproj, etc) can be included by multiple solutions (sln files). Thus a project can be shared by multiple independent solutions.
- Avoid having dependencies across team projects and try to have all the related solutions/projects under same team project. This will minimize the need for customization of build scripts.