Using Vault 3.0.6 Client with VS Whidbey Beta 2 Gold

mark.brown · Post by **mark.brown** » Sat Apr 30, 2005 7:02 pm

We've had pretty good success using Vault 2.x as our SCC provider with VS Whidbey Beta 1 (and even interim builds).

We just upgraded to Vault 3.0.6 Server and Client and now I'm getting "Object reference not set to an instance of an object" exception when I attempt to add a VS Solution to Source Control. This happens immediately after attempting to logon to Vault.

We found another post that suggested specifying the framework version that Vault should use in the VaultGUIClient.exe.config as follows:

<startup>
<supportedRuntime version="v2.0.50215" />
</startup>

Unfortunately, this doesn't appear to have any effect...

Is there possibly an alpha/beta version of the Vault client that we might be able to try out that is designed for VS Whidbey?

-Mark

dan · Post by **dan** » Sun May 01, 2005 9:33 pm

We will have a beta of Vault 3.1 available sometime this month that will work with Whidbey Beta 2. If you email support at sourcegear.com, we will add you to the list of people who will recieve advance notice of its availability.