I suspect they're talking about breaking up your Web Project into multiples such as business objects and the actual Web app, that's why they have two projects.
I don't use source safe, but I basically use this exact structure for my apps and the reasoning for this is if you ever need to distribute your app it's easy to pick up the whole things and move it just by selecting a few directories.
In my case I often also put the SLN file into the directory of the main project (in this case the Web app).
Really not sure what hte benefit is to match exactly the structure of VSS. The whole point of VSS's internal setup is that it is a virtual mapping of a project. The main point I think is that when somebody downloads this project they get a self contained structure that matches the original setup. It's important that relative directories are the same so that the solution file can find the sattelite projects. From that aspect I don't think it matters that you match everything exactly just that the projects are isolated in such a way that they can be easily accessed relative to the Solution's path. This mainly means NOT using the default in My Documents <g>...
FWIW, if you work with generic code that is reused across projects that won't work anyway, so the value of this suggestion is very limited anyway.
+++ Rick ---
>The Patterns and Practices Team Development with Visual Studio .Net and Visual SourceSafe document recommends that the file structures for the VS solution and VSS should match.(see below)
>
>
>Local Machine VSS Project Structure
>\Projects $/Projects
> MySystem MySystem
> MyWebAppSolution MyWebAppSolution
> MyWebApp MyWebApp
>
>
>I create a solution according to the document and add it to VSS and get the following structure
>
>Local Machine VSS Project Structure
>\Projects $/Projects
> MySystem MySystem
> MyWebAppSolution MyWebAppSolution
> MyWebApp MyWebAppSolution
> MyWebApp
>
>How can I get the recommended VSS structure?
>
>Thanks
>
>Rex
