Visual Studio 2005 support?

mculbreth · Post by **mculbreth** » Tue Feb 22, 2005 6:44 am

Howdy,

Will Vault support the new protocols for Visual Studio 2005 when it is released later this year? I know that Microsoft is releasing Team System along with it, but hopefully it will still work with the old SCCAPI. Any ideas?

Thanks,

Matt

dan · Post by **dan** » Tue Feb 22, 2005 8:29 am

Yes, Vault will work with both VS 2005 and continue to work with VS 2003 (as well as VB6 and VC6). We are planning a 1.1 release in the next few months that will work with Whidbey (VS 2005).

mlippert · Post by **mlippert** » Wed Feb 23, 2005 4:12 pm

Small correction. I'm pretty sure you mean a 3.1 release

dan · Post by **dan** » Wed Feb 23, 2005 8:54 pm

Doh! Yes, 3.1 would be the right number there - thanks!

mculbreth · Post by **mculbreth** » Tue Mar 29, 2005 1:50 pm

As an FYI--this seems to work already. I'm able to create a new solution in VS.NET 2005, add it to Vault, check-out/check-in, etc.

Am I missing something here?

dan · Post by **dan** » Tue Mar 29, 2005 2:40 pm

It works rather intermittently on Whidbey - not enough for us to call it supported yet. Also, you might still be using the 1.1 .Net framework, which should work fine - Vault's problems with Whidbey are mostly due to the 2.0 framework.

mculbreth · Post by **mculbreth** » Tue Mar 29, 2005 2:42 pm

Ok, thanks.

If we were to do most of our work through the Vault client when doing VS.NET 2005 work would that be ok? Assuming we get the initial solution created and bound properly of course.

dan · Post by **dan** » Tue Mar 29, 2005 2:51 pm

Yes, the Vault GUI client should be able to work side by side with Whidbey without problems.

CraigNicholson · Post by **CraigNicholson** » Fri Apr 22, 2005 12:58 am

Currently I'm running Vault 2.0.6 and we have no need to upgrade to Vault 3.0 as we don't require any of the new the feature-set THAT much.

When it comes to Visual Studio 2005 Beta 1 a developer noticed that the IDE plugin pretended to do a check-in/add and didn't actually. When launching the Client it reported "The working state information for xx is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibility exception was: Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks"

I haven't tested with Visual Studio 2005 Beta 2 as yet, but I'd like to know if any of these issues are intended to be fixed in the 2.x product line and when that is likely to be?

dan · Post by **dan** » Fri Apr 22, 2005 7:35 am

We will have support for Whidbey with Vault 3.1, and there will be a Beta available in May. We don't have plans to make Vault 2.0.x compatible with Whidbey.

CraigNicholson · Post by **CraigNicholson** » Fri Apr 22, 2005 7:46 am

dan wrote:We will have support for Whidbey with Vault 3.1, and there will be a Beta available in May. We don't have plans to make Vault 2.0.x compatible with Whidbey.

Do you at least have a way for VS2003 and VS2005 to be used on the same machine while Vault is registered as the default SCC for VS2003 only and for VS2005 to use another?

If your product is not going to be compatible with VS2003, it should not even load under VS2005 and hence prevent corruption of data. Don't you agree?

dan · Post by **dan** » Fri Apr 22, 2005 8:02 am

Visual Studio doesn't have a way to load different SCC providers for different versions of VS - it uses the same registry setting in both versions.

Vault 3.1 will be compatible with both VS 2003 and VS 2005, so you shouldn't have a problem if you upgrade.

CraigNicholson · Post by **CraigNicholson** » Fri Apr 22, 2005 8:13 am

dan wrote:Visual Studio doesn't have a way to load different SCC providers for different versions of VS - it uses the same registry setting in both versions.

Vault 3.1 will be compatible with both VS 2003 and VS 2005, so you shouldn't have a problem if you upgrade.

Firstly I should not need to upgrade Vault if I install another development IDE onto my machine. It should either work with VS2005 or it should not load at all under VS2005. Don't try and force me into upgrading to Vault 3.1.

I don't need to upgrade to Vault 3.1 as I don't need any of the new features. Sure I'd like to have integration from VS2005, but its not worth the upgrade cost.

Just make your existing product co-exist with VS2005 properly.

dan · Post by **dan** » Fri Apr 22, 2005 9:26 am

Vault 2.0/3.0 does co-exist with Whidbey - it just doesn't work. It doesn't corrupt any data that I'm aware of.

Yes, displaying a message that a future version of Visual Studio may be incompatible with this version of Vault would have been helpful. But, once you know it doesn't work, it doesn't require a new version of an older version of Vault to not load it.

mlippert · Post by **mlippert** » Fri Apr 22, 2005 9:29 am

I'm just curious.
Why is it that you feel that SourceGear should provide you with a free upgrade to support a new Microsoft version, but that you don't feel that Microsoft should provide you with a free upgrade that continues to support SourceGear's product?

I think that's just a rhetorical question.

Mike

SourceGear Support

Visual Studio 2005 support?

Visual Studio 2005 support?

Compatibility exception around DateTime ticks