Guidelines on structuring solutions and projects in team build

1. Single solution is best for small size projects.
2. The most scalable and efficient way for managing and building large applications is team build is to have multiple independent solutions.
3. Always avoid solution to solution references. They are not supported in Whidbey.
4. Editing “Microsoft.TeamFoundation.Build.targets” file is (strongly) not recommended.
5. 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.
6. 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.

Comments

• Anonymous
  June 20, 2006
  Hello Manish:
  While its good to inculde multiple project files, in a solution. I would like to know if I could re-order, arranage and if possible change the name of the logical folders in the solution. The solution file is XML file, I would like to know if we can get specifications of the XML used for solution files in SQL 2005 Management Studio.