Adding solutions to VSS = Frustrating

I'm pretty much at my wits end with this, so it's open to the forums!!

My environment is as follows:

Visual Studio 2005 (vb.net 2.0)
Visual Source Safe 6
Windows Vista Home Premium

I have a solution with two projects:

Solution 'Online Transactions' (2 Projects)
   + OnlineTransactions
   + OnlineTransactionsSetup

The properties for the "OnlineTransactions" project contains a Root Namespace of:

"CompanyName.ProductName.Modules.OnlineTransactions"

The folder structure on my computer is:

C:\Users\Simon\Documents\Visual Studio 2005\Projects\CompanyName
\ProductName\Modules\Online Transactions

*** I am now trying to check this into source safe***

I currently have a project tree as follows:

$/ProductName/Modules/

When I try and "Add solution to Source Control" from Visual Studio, I expand the tree to the 'Modules' folder, delete the "Online Transactions.root" entry in the Name field, and click on OK.  This is what is created in VSS:

$/ProductName/Modules/Online Transactions/CompanyName/ProductName/Modules/OnlineTransactions
$/ProductName/Modules/Online Transactions/CompanyName/ProductName/Modules/OnlineTransactionsSetup

This is not right!! What I really want is:

$/ProductName/Modules/Online Transactions/OnlineTransactions
$/ProductName/Modules/Online Transactions/OnlineTransactionsSetup

Why is VSS / SCCI / VS 2005 forcing the root namespace to be part of the
sourcesafe structure?

I have also tried:
 - Removing the Root Namespace, leaving only the project name in here... somehow it has remembered the previous root namespace and checked the solution in incorrectly again.
 - Adding all files manually to VSS and binding the project through VSS... this time Visual Studio decides to show the files as 'awaiting check in', then checks them in the incorrect structure.


Could someone more into this stuff than I please give me some advice on checking solutions into sourcesafe?!

Thanks
Simon
Start Free Trial