REquired field/property VautService.VaultAuthValue of ....

[mistergerf]

(Just downloaded latest eval version.)

"REquired field/property VautService.VaultAuthValue of SOAP header VAultAuth was not set by the client prior to making the call."

I get this when trying to log onto the server from my Vis Studio IDE to add a solution to the vault. I've read the post by one user about switching the .NET version running on the server and have changed VaultService and VaultShadowFolder .NET versions using the tool suggested. I've also rebooted the server ... all to no avail.

Is there something I have to change on the client side too ? I'm pretty sure my Vis Studio version is using .NET 1.0.

g

[dan]

If you are running Visual Studio 2002, then yes it does use the 1.0 framework, and the IDE component won't work with it. The client requires .Net 1.1 to run, so you'd have to upgrade to VS 2003 to use Vault integration.

Note that the GUI client will work as long as the 1.1 framework is installed on the machine.

[Jim Clark]

I sure wish I had read about this before I spent all weekend importing our large .NET 1.0 application to Vault

Oh well, hopefully we have to opportunity to convert our application to 2.0 within the next 18 months or so. Until then it's back to VSS

[dan]

Note that this limitation applies only to VS2002 and the VS IDE component. VS 2003 works fine, as does the Vault standalone GUI client, so either of those paths are available for using Vault for SCC on an app that needs the 1.0 framework.