Kev,

>How would this work? Is it possible for me to store the class libraries in a sourcesafe project and pull those libraries down, into another project?

We find it easiest to have VSS directories the get replicated on each developers box

\base
   \dev
      \classes
      \forms
      \...
   \test
      \classes
      \forms
      \...
   \prod
      \classes
      \forms
      \...

\projectA
   \dev
      \classes
      \forms
      \...
   \test
      \classes
      \forms
      \...
   \prod
      \classes
      \forms
      \...

\ProjectB
   \dev
      \classes
      \forms
      \...
   \test
      \classes
      \forms
      \...
   \prod
      \classes
      \forms
      \...

All the common code is in the base tree. Using Dev, test and prod folders allows the code to have various stages of development going at the same time. Developers work with code in the dev tree. as code moves to test it's pinned and shared into the test tree, once it passes test it's pinned and shared into the prod tree. Each project gets its own folder. You can introduce a client level above projectX if you develop more than one major system for a client. The project folder can easily contain multiple apps if they are built off the same code.

You just need to Get Latest on the VSS folder as appropriate but all work is done on the local machines not network drives, this avoids the file sharing conflicts I mentioned.

This is just one way to layout things, I'm sure others have used different methods.