Hi,
We have been using Vault with VS2003 successfully in our office and over VPN's for some time.
We are also using VS2005 for a new project and now have serious problems with source control and VS2005. These problems include:-
VS2005 electing to check out certain project files on loading a solution
The solution explorer not displaying source control information status information - e.g. whether a file is checked out or checked in etc.
Check In's mostly fail from VS2005 Solution explorer.
Check Out's can fail too from VS2005 solution explorer
Vault often shows files with Renegade or Needs Merge status after working on a project.
Have you, or other users experienced these problems with VS2005 and Vault? Is there a work around or a patch available from either Microsoft or Sourcegear?
It should be noted that all workstations running VS2005 and Vault all experience these kinds of problems - i.e. it is not a machine specific problem.
many thanks
Ralph Weedon
(our vault client is 3.0.7. We are running Windows XP Pro, Vault on SQL Server 2000, VS2005 version: 8.0.050727-4200).[/list]
vs2005 vault integration problems
Moderator: SourceGear
Full support for Visual Studio 2005 was not implemented until Vault 3.1. That is probably the cause of the behavior you are seeing.our vault client is 3.0.7
To use VS 2005, upgrade to 3.1.6, our latest release. It's a free upgrade since you have a 3.x license. Both clients and server should be upgraded.
Details here:
http://support.sourcegear.com/viewtopic.php?t=4294
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 2
- Joined: Thu Jan 26, 2006 10:21 am
Thanks for the reply.
I have an office PC and a PC at home. The office PC was running vault 3.0.7. However after I posted the message I checked my home machine and the machines of the other two developers attempting to use vault with vs2005. They are all using Vault client 3.1.5 together with a server version of 3.1.5.
We will upgrade to 3.1.6 and see if that helps.
I have an office PC and a PC at home. The office PC was running vault 3.0.7. However after I posted the message I checked my home machine and the machines of the other two developers attempting to use vault with vs2005. They are all using Vault client 3.1.5 together with a server version of 3.1.5.
We will upgrade to 3.1.6 and see if that helps.