Vault and .NET Integration Error

Tom · Post by **Tom** » Mon Mar 14, 2005 9:51 am

I have converted my Visual Source Safe project to Vault. I have installed the Vault client on my development work station.

But when I launch Visual Studio .NET, I am getting this Vault error recursively when I try and open my project:

"Object reference not set to an Instance of an Object!" Press OK.

Can anyone assist?

Thanks

Tom

dan · Post by **dan** » Mon Mar 14, 2005 10:42 am

Are you using Visual Studio 2002? This error happens in VS 2002, because it cannot load the .Net 1.1 framework, which Vault requires.

Tom · Post by **Tom** » Mon Mar 14, 2005 10:55 am

Dan:

Yes I am using Visual Studio version 2002. Are you saying Vault does not work with VS2002? I find this hard to believe but if I have to upgrade to 2003 I can. Are there no patches or fixes for VS2002?

Tom

dan · Post by **dan** » Mon Mar 14, 2005 11:08 am

We had a patch through Vault 2.0.6 that worked with VS 2002, but did not extend the patch into Vault 3.0. If you can upgrade to VS 2003 without too much trouble, that would be the way to go. Sorry for the inconvenience.

Tom · Post by **Tom** » Mon Mar 14, 2005 1:18 pm

Dan:

Well I checked with the other developers and all but 10 can upgrade to VS2003. So do you have a fix for those VS2002 developers or am I stuck wiht supporting two source controls?

Tom

dan · Post by **dan** » Mon Mar 14, 2005 2:09 pm

We don't have a patch for VS 2002 with Vault 3.0, but those developers could use the Vault GUI Client to do source control until they can upgrade to VS 2003.

If you use two different versions of Vault, they will need to be on different servers, so that may not work out so well if you want everything within a single Vault server.

Tom · Post by **Tom** » Wed Mar 16, 2005 2:35 pm

So help me out here.

I now all but one developer that can't upgrade to Visual Studio 2003. He must stay at VS 2002!

So it the latest version 3.05.2833 does not support VS200, what options, it any, do I have? Can I install a previous client version that works with VS2002 or is not a good idea to use an older client version with a newer product?

Thanks

Tom

dan · Post by **dan** » Wed Mar 16, 2005 3:24 pm

If your server is on 3.0, then all yours clients will need to be as well, due to protocol changes between versions.

That one developer can use the Vault GUI client until he can upgrade to VS 2003, so he can still have access to source control.