title: TFS 2010 - how should VS solutions with shared libraries be mapped into "team projects"?
body: <p>I'm new to TFS (and branch/merge style source control).  I've been reading through the TFS Branching Guide for 2010, but I'm having a bit of a disconnect with how my solutions should be mapped to the source control.  I think my main problem is how to understand th best placement of class libraries shared between solutions.</p>
  
  <p>Our environment is line-of-business with about a dozen separate web applications and about half a dozen class libraries shared between the web applications.  Our solutions generally consist of one of the web applications, it's unit testing project, the supporting class library projects, and any third-party assembly references.</p>
  
  <p>So two representative solutions would look like:</p>
  
  <p>SOLUTION A<br/>
  -- WebApp11 Project<br/>
  -- WebApp11UnitTests Project<br/>
  -- ClassLib11 Project<br/>
  -- ClassLib22 Project<br/>
  -- ClassLib33 Project<br/>
  -- bin\*.dll<br/></p>
  
  <p>SOLUTION B<br/>
  -- WebApp22 Project<br/>
  -- WebApp22UnitTests Project<br/>
  -- ClassLib11 Project<br/>
  -- ClassLib22 Project<br/>
  -- ClassLib44 Project<br/>
  -- ClassLib55 Project<br/>
  -- bin\*.dll<br/></p>
  
  <p>How should these be structured in TFS? </p>
  
  <p>Do we create a Team Project for each Solution, such that ClassLib11, for example, would belong to both TEAM SOLUTION A and TEAM SOLUTION B? </p>
  
  <p>I'm thinking yes, so that each Team Project consists of everything required to roll out into production.</p>
  
  <p>What if we use a couple different solution files, such as having one large solution file that has every web application and every class library?  Where does that solution fit in?</p>