Backwards Compatibility

[rgrayson]

I have been using Vault (single-user) at home as a means of source control, and am a long time fan.

I am a contract programmer, so move around from company to company quite a bit, and have recently started work at a company that also uses Vault. Unfortunately, they use version 4.x and I am on version 5.x and have found out that I cannot use the same client to access both servers.

If you are not going to make clients backwards compatible, could you at least allow multiple versions of the client to be installed?

Has anyone else here come across this and found a workaround?

Thanks,
Robin.

[Beth]

We don't support multiple clients being installed, because we don't test that way, but there is a way to run two clients. This might take uninstalling your latest version. I haven't tried installing in reverse order or newer then older, so I don't know what the results would be.

The basic instructions are:
1) Install the oldest version first.
2) Go to the location that Vault was installed to and move the folder to a different disk location.
3) Install the second version of Vault, but install to the original location the first one was installed to.

The short-cuts are taken over the the newest version of Vault, so you may want to make some short-cuts from the original Vault install. The IDE integration is also taken over by the newest install, so you might try a registry switcher program to give yourself a way to use integration with both. Otherwise, you can use the older version non-integrated with VS and the new one integrated with VS.

We can't guarantee that everything will function with two clients.

[rgrayson]

I've got 4.1.x and 5.0.2 installed now ... thanks, should help a bit.

I'm guessing that the IDE will be hooked up to the 5.0.2 client ...... don't suppose there are any registry hacks that will allow that to be switched are there (unofficially, and unsupported, of course!)

[Beth]

We have a KB article that talks about the registry key to flip: http://support.sourcegear.com/viewtopic.php?t=4010. There are registry switchers out there that can do the flip of the keys in a few clicks, and there are SCC switchers I think that will do the same thing.

[rgrayson]

That's great thanks!

I'll give that a go tomorrow.

[Beth]

You're welcome.

[coderanger]

Would creating a separate Windows login user for the two different scenarios help? Then if you are working privately you logon to your profile, if working for the company you login to a different profile ... no need for separate reg key switchers or anything.

[Beth]

I haven't tried it, but the source code provider keys are under HKEY local machine and not the HKEY current user. I thought the keys had to be under HKEY current user in order for a profile to have different settings. It might be worth trying out.

[coderanger]

Yes of course, you are quite right, this was always the problem from the beginning wasnt it. Oh well, sorry for confusing the post.

[Beth]

I thought it was a good idea though.

[VOORSPRONG]

Has Sourcegear given the non-support for multiple clients another thought perhaps for version 6? We have now three different versions to use as developer. Some of our customers use version 4.x, some use version 5.x and some use version 6.x. I would be great if the Vault GUIClient would be able to connect to the different server versions. I can install multiple clients and until last week I had two vault icons on the desktop to pick from but now I have THREE!. Worried about version 7...

[Beth]

I can log a feature request for a backwards compatible client. Thank you for your feedback.

F: 16742

[VOORSPRONG]

Would appreciate that. Hope it is honoured (soon).