This book came recommended in the latest issue of Software Development magazine:
http://www.pragmaticprogrammer.com/starter_kit/vc/

It is not about VSS per se, but it might have good ideas for what you are looking for.

>Hi All,
>
>My company is developing a web application that has a main module and other modules that can be turned on after purchase. We are currently using VSS integration with VS.NET 2003. We need some help with branching, pinning and sharing. Our setup is one VS.NET solution with 19 separate projects. We have projects for each module and projects for different kinds of business objects, report objects, and typed data sets.
>
>Our main module contains a lot of old ASP code. We have just completed the first round of development on the second module and are in the process of developing a third. Before we get knee deep in developing this new module, we would like to set up VSS to allow us to track and release different versions of each module. Right now our setup is forcing us to release both modules. If we aren’t done developing in one or the other we can’t do a release. We’d like to be able to release modules separately as new functionality is added or bugs are fixed.
>
>I really appreciate any advice you can give me. We’ve searched high and low and haven’t found and good material on how to really integrate VS.NET 2003 with VSS. Does anyone know of any other version control software that might be better to use with VS.NET? Do we even have our Solution structured properly?
>
>I’ve asked the resident VSS expert Ted Roche and he feels that MS is neglecting VSS far worse than VFP and Ted hasn’t worked with .NET. Anyone else got experience with this?
>
>TIA,
>
>Jacci