Maybe I was dumb thinking it wouldn't hurt upgrading Vault, but I did anyway for their new features (Find in Files for example) and for the code everything is fine in VS2010, however SSC 3 has stopped working. Get Latest tab returns error "Server version not supported".

Vault 6.0 has been out for a little while already. Any plans to bring SSC 3 on par with this new version? Any early access release we could use in the meantime?

While trying to setup a custom config xml file for interfacing with Vault 6.0 command line fails (CLI parameters do not properly map to available macros in the xml file + you need to put credentials straight in the CL), I manage to get things working by providing a blank config xml file (no commands for all source control calls). The effect is that while it does not at all interact with the Source control client, it still commits/gets changes using my local drive working folder as the reference. From there I can get/check out/check in using my standalone Vault client.

Although working this way requires more manual work, I came across one benefit of using SSC this way: it's allowing you to commit (check-in) code AND database as a single changeset, since you're controlling everything from your source control client.

Also, in the meantime, it would be good to have your product page state that this new version isn't supported. The way it's currently worded does not suggest that at all (it says "Vault 5.1 and later").

Hmmm... well it seems things could have been much more simple if I had the following idea sooner.

I found files under
C:\\Program Files (x86)\\Red Gate\\SQL Source Control 3\\Vault
All those DLLs are from Sourcegear and of version 5.1.1

By copying the same DLLs from my Vault 6 folder into the above folder (and overwriting the 5.1.1 DLLs with 6.0.0), and restarting SQL Source Control/SSMS, now I can link to Vault again and Get Latest/Commit works just fine.

This is a much easier way to proceed than trying to do command-line hooks or manually check out/in files with the Vault client...

Again I thought I'd share what I found in case someone else out there is in the same pain I was since upgrading to Vault 6... now pain is gone

Thank you so much for posting this work around. I mistakenly upgraded Vault also, thinking it would be no big deal. Definitely a big oops on my part, but so far at least, this solution is getting me by. Hopefully a supported solution will be available soon.

Just a heads-up - the latest release of SQL Source Control, which is 3.1.0.4829 should introduce full support for Vault 6. It's available via the Check for Updates functionality within the tool or from our ftp site here: ftp://support.red-gate.com/patches/SQLS ... 0.4829.exe

andy.campbell.smith wrote:Just a heads-up - the latest release of SQL Source Control, which is 3.1.0.4829 should introduce full support for Vault 6. It's available via the Check for Updates functionality within the tool or from our ftp site here: ftp://support.red-gate.com/patches/SQLS ... 0.4829.exe

What would "The Server edition is correct, but the version is wrong" error indicate? I have installed v3.1.0.4829 and have Vault Standard 6.0.1.598.

andy.campbell.smith wrote:Just a heads-up - the latest release of SQL Source Control, which is 3.1.0.4829 should introduce full support for Vault 6. It's available via the Check for Updates functionality within the tool or from our ftp site here: ftp://support.red-gate.com/patches/SQLS ... 0.4829.exe

What would "The Server edition is correct, but the version is wrong" error indicate? I have installed v3.1.0.4829 and have Vault Standard 6.0.1.598.

Apparently this is only works with Vault 6.0, not 6.1. The dlls are version 6.0.0.477, not 6.0.1.598.