title: Questions about reorganizing Visual SourceSafe projects
body: <p>I have inherited a very disorganized VSS database and I need to clean it up.  Before I finalize my reorganization, I would like to get some guidance so I don't make similar mistakes as the previous person.  I'm going to move everything to a new instance of VSS and start fresh.  Historical information isn't a concern, so it is understood that the fresh install will not include history of prior versions.  (The current VSS db will be available if needed.)</p>
  
  <p>We are currently using Visual Studio 2005 and Visual Source Safe 2005.  We'll be moving to VS2010 and perhaps TFS, but first steps first. </p>
  
  <p>We have three ASP.NET products, each of which share multiple libraries.  Here's the basic structure of the projects:  </p>
  
  <pre><code>PRODUCT 1  
      References:  
          Library 1  
            References:  
              Library 4  
              Library 5  
          Library 2  
          Library 3  
  
  PRODUCT 2  
      References  
          Library 1  
              References:  
                  Library 4  
                  Library 5  
          Library 3  
          Library 6  
  
  PRODUCT 3  
      References  
          Library 5  
          Library 3  
  </code></pre>
  
  <p>As a first step I have all of the products and libraries "Unbound" from VSS and have structured them in folders as follows.  (There are 3 developers and we'll all setup the same folder structure on our machines.)</p>
  
  <pre><code>C:\Source\Products\Product1  
  C:\Source\Products\Product2  
  C:\Source\Products\Product3  
  C:\Source\Libraries\Library1  
  C:\Source\Libraries\Library2  
  ...  
  C:\Source\Libraries\Library5  
  </code></pre>
  
  <p>Each Product and Each library has it's own solution; project references are used for all referenced libraries.  For example, the solution for PRODUCT 1 includes project references for Libraries 1, 2, 3, 4, and 5.  The solution for Library 1 has project references for Libraries 4 and 5 and so on.  Everything builds at this point.  </p>
  
  <p><B>Question</B>:  Is it common practice for PRODUCT 1 to include project references for Libraries 4 and 5 even though it doesn't reference them directly (Yet one of its referenced projects does)?</p>
  
  <p>I plan to setup a parallel structure in VSS:</p>
  
  <pre><code>$\Prodcuts\Product1  
  ...  
  $\Libraries\Library5  
  </code></pre>
  
  <p><B>Question</B>:  Is this a logical structure to be using?  If not, what should I do different.</p>
  
  <p>Thanks in advance for your input.</p>
  
  <p>Darvis</p>