So as we all know Vault and Whidbey/VS2005 don't like each other so much. I have it limping along at the moment, so long as I never use the Vault client itself, and use a totally separate respository, it mostly works.
But my general issue is that given that as developers we need to be out in front of the VS2005 and C# 2.0 release, we really need source control for this product, even in beta stage. If we can't get it, we have to find some other solution and that would not be a happy day.
How can we help you get this working properly?
VS2005 / Whidbey and Vault
Moderator: SourceGear
We plan to have full support for Whidbey in the 3.1 release of Vault, which will be coming out in the next few months.
We already have an early Beta of 3.1 that seems to work pretty well, but are still in the process of testing it more thoroughly. If you'd like to get an early copy to test against, let me know, and we can provide one for you.
We already have an early Beta of 3.1 that seems to work pretty well, but are still in the process of testing it more thoroughly. If you'd like to get an early copy to test against, let me know, and we can provide one for you.