Note that there are some explanatory texts on larger screens.

plurals
  1. POPartitioning a project into multiple solution
    primarykey
    data
    text
    <p>I'm managing a mid-size project in VS2010 (and TFS2010). We have separate teams for different parts, and a team for a "common" part which will provide frameworks and such. Source structure:</p> <ul> <li>Common</li> <li>+--- CommonLibrary1</li> <li>+--- CommonLibrary2</li> <li>+--- etc.</li> <li>Part1</li> <li>Part2</li> <li>etc.</li> </ul> <p>Requirements:</p> <ul> <li>A dev in the "Common" team should use Common.sln that contains only Common code</li> <li>A dev in the "Part1" team should use part1.sln that contains part1. It references stuff from Common, and should be able to build that stuff (same for part2, etc.)</li> <li>If a dev in the "Common" team create a new "CommonLibrary3" project, I only want to update Common.sln - I don't want to touch Part1.sln, etc.</li> <li>TFS build should always build everything</li> </ul> <p>Non-requirement:</p> <ul> <li>TFS-build of just Part1. All of this is a single project, and is always released together.</li> <li>Separate management of parts.</li> </ul> <p>Sub-optimal solution I know of:</p> <ul> <li><p>Add Common.sln to part1.sln - seems like VS just copies all project from Common.sln into part1.sln, so projects later addede to Common are not included.</p></li> <li><p>Replace solution files with MSBuild target files - <a href="http://sedodream.com/2010/03/19/ReplacingSolutionFilesWithMSBuildFiles.aspx" rel="nofollow">http://sedodream.com/2010/03/19/ReplacingSolutionFilesWithMSBuildFiles.aspx</a>. I guess that would work, but I want the devs to update solutions from VS, not hand-edit MSBuild files.</p></li> </ul> <p>The TFS Guide books I found calls this a "Partitioned Solution", but doesn't specify how to actually achieve it.</p> <p>Any recommendations?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload