Major problems using Vault on different machines

[Beth]

coderanger: I'll get that checked out here too.

Russ Freeman: If your issue isn't the same as coderanger's then we should start a new thread to look at what's going on in your case. Also, take a look at the additional document I posted about having projects under multiple solutions.

[Beth]

coderanger: So that I can try reproducing the issue here, can you tell me the exact project types you are using?

[coderanger]

The reusable components are plain C++ Libraries and the main Product solutions are Windows32 C++ or MFC apps.

[Beth]

Were the .vspscc and .vssscc files actually in VSS before you performed the hand-off and so now they are in Vault, or were in Vault prior to you deleting them? Or were those files only present on disk in your working folder? I believe you said they were actually in Vault from the hand-off, but I wanted to make sure.

Also, when did you upgrade from VC6 to VS2008? Was that before or after you moved from VSS to Vault?

[coderanger]

I need to investigate this further as the problem appears to still be there. The vspscc and .vssscc files were in VSS as Visual Studio added them, these were then handed off to Vault and thus were then in Vault and I believed were causing Vault problems; but I am not entirely sure its just that ... we still cant open up projects between different users at the moment and its becoming a complete waste of time.

As I said, I have to spend a bit of time investigating it and will post back anything I find.

[Beth]

I've ran some tests as well, and found that I was only able to reproduce the issue you are having if I open the solution by double-clicking the .sln in Vault. Double-clicking the .sln in Vault doesn't open the solution from the disk location. By default, it uses the View functions, which pulls down a copy to a temporary location and opens that rather than from the working folder. You won't want to use that route.

The first binding of this solution may seem difficult because some of the projects are not located directly beneath the solution, and that scenario requires a few more steps. Once it's bound, it should still work fine. I've attached a document that has step-by-step instructions.