Vault & VSS on same machine

[kankele]

We use Vault (version 4) internally, but some of our clients use VSS so I need to have both clients on my machine. So I have a couple of questions
1. Is this supported?
2. If so, should VS2005 automatically use the correct provider based on the solution I am opening?
3. Currently I have a VSS bound solution. I go into VS2005, set my source code provider to VSS, then open the solution at which point I get the Vault connect dialog. Any ideas??

Thanks for any help you can provide

[Beth]

You can have Vault and VSS on the same machine.

Are Vault and VSS working on the same projects or solutions? You can't have a project bound to both.

[kankele]

Vault and VSS are targeting completely different solutions and projects. There is no overlap.

[Beth]

Do you have Vault set to be your default SCC provider? If so, I think you will want to turn that off. (In the Vault client - Tools - Options - General)

Also, can you confirm that no other users have mixed up which is used for which project?

Had you performed an Open from Source Control on that using VSS before? If not, then you will need to do that to set bindings. If it was working before Vault, then this probably isn't the issue, but setting Vault as the default may still be a problem.

[kankele]

Vault is currently set as the default SCC provider. If I un-check this selection, press OK, then restart the client it is checked again. I cannot seem to get it to stay un-checked. Actually, I don't need to even exit Vault - I just click ok, then go back into the options screen and it is checked again. The client and server version are 4.1.0.16216

[Terence]

Are you running a 64-bit operating system?

[kankele]

No. Server is 32 bit win2003 server and client is 32 bit XP Pro

[Terence]

Regarding the solution that's causing the problem, is it in the Vault repository at all?

Maybe following these steps will help.

1. Open the solution like normal.

2. When it asks you to log into Vault, choose cancel.

3. Agree to work offline (disconnected)

4. Go into File->Source Control->Change Source Control

5. Unbind everything in the solution

6. Exit the dialog and Save All

7. Close Visual Studio and re-open it

8. Choose VSS as default provider

9. Open the problem solution

10. Rebind to VSS via File->Source Control->Change Source Control

[kankele]

The solution causing the problem is not in vault at all, just in VSS. I am reluctant to go through the un-bind process as the solution is one of our customer's projects with many developers working on it. I want to be pretty certain that the solution is the problem before I request to do that.

I did find out one more piece of information. I have a few VM's that I use so I have the vault client instead a number of times. On one VM that does not have VS2005 installed, I can sucessfully check and un-check the default SCC provider checkbox in the Vault client. This made me realize that in the VM where I am having the problem, the default SCC provider checkbox is not actually "checked", but rather has a solid box filling the checkbox. This solid box is what I cannot clear. I un-installed the vault client and re-installed and I get the same behavior.

[Terence]

Binding and unbinding the solution will not do it globally, but only for the machine where it is unbound. As long as you don't check anything in.

So it's completely safe to follow the suggested steps on either of your VMs.

The Enable Vault as SCC Provider check box is a tri-state check box. This is because, although you may un-select it for Visual Studio 2003, you may still have it selected for VS 2005 or VS 2008.

When opening the dialog, it reads if *either* of those has Vault set as the SCC provider and shows it accordingly.

The way to completely clear it, is to go to each VS 2005 and VS 2008 and un-select Vault. Then open the Vault client and un-select that option.

It is my suspicion that the state of that check box is not related to the problem you're experiencing, but I hope this helps.

[kankele]

Well, everything is working now. I'm not sure what I did to fix things. I deleting my local files and did a get latest a couple of times plus I uninstalled and re-installed vault a couple of times.

My take away on this is if it ever happens again I should probably start with unbinding the problematic solution and re-bind to see if that fixes the problem?

Thanks for your help

[Terence]

You're quite welcome. We'll be here, should this problem ever come back.

[JBLarcomb]

I'm having this same issue (unable to remove Vault as default SC), with one possible exception: If I open VS 2005 with Source Control set to VSS (Tools->Options->Source Control) and either open the solution via menus or drag the .sln file onto the open VS 2005, the project opens as expected (using VSS). If you double click the .sln file, however, it opens VS 2005 with the Source Control set to Vault, which causes a train wreck.

As stated above by another user, I am unable to un-check "Make Vault your default SCC Provider" within the Vault Windows client (Tools->Options->General). It is permanently greyed-out (the check box, that is). I click it, it clears. I close the window. Open it again (Tools->Options->General) and it's grey again!

This makes for a very frustrating evaluation. The folks I need to convince (to switch to Vault) are very unimpressed.

Please help!

[Beth]

Did you try the steps mentioned above? Are you wanting the solution completely unbound or bound back to VSS? There is a process to it, and there's no work-arounds to this process. Going through the unbind process is the only way.

Maybe following these steps will help.
1. Open the solution like normal.
2. When it asks you to log into Vault, choose cancel.
3. Agree to work offline (disconnected)
4. Go into File->Source Control->Change Source Control
5. Unbind everything in the solution
6. Exit the dialog and Save All
7. Close Visual Studio and re-open it
8. Choose VSS as default provider
9. Open the problem solution
10. Rebind to VSS via File->Source Control->Change Source Control