OT: Can someone explain the VS.NET project.root philosophy?

[erict]

Sorry for probably asking a dumb question about VSS -- we have purchased Vault but I'm not switching over until next month. I just added a VC++.NET project to VSS, and even though all the files were in a single directory with just one project in the solution, when I added to VSS it created a project.root and then within that a project were all the files are. The project.root only contains the project, nothing else. What's the point of creating the project.root?

Thanks for anybody explaining the philosophy behind the .root system.

Also how should I fix my directory tree / project tree difference now. Three options: A) change VSS to match my directory structure by getting rid of project.root and moving project up B) create a project.root directory and move my project directory into the project.root directory C) override the default working directories and effectively 'remove' the project.root for GETs

[dan]

I'm not familiar with how project.root works - it is probably a Visual Studio thing.

It is always best to match the structure that Visual Studio wants you to have when integrating with source control. Fighting it by trying to override defaults and such will mostly leave you frustrated.

[erict]

That's what's weird. The directory structure was decided by Visual Studio.NET. I just started a new managed C++ project. Then I put everything into VSS, from within Visual Studio. How does it do it in Vault? Do the project names come from the Vault client or from the VSS SCM interface? And because everything was decided by VS.NET/VSS, I now have a difference of opinion between the two as to the locations of the files. VS.NET has all the files in project, while VSS has all the files in project.root/project So I need to change something.