Hi
we just migrated from Vault 3.5 to Vault 5.0. Everything is working fine with the exception of a module that is being checked out every time a user opens a solution.
Our application has many interface projects under one solution, and many solutions use the same interface projects. that's because each solution is a sub-system of the whole.
So when user A opens solution A, all interfaces (including the one we're having problem) are opened with it. When this happens, Visual Studio (VS) checks out interfaceprojectA (without request), all other interface projects are just opened, not checked out.
When user B opens solution B, VS tries to check out interfaceprojectA, not sure why it's trying to do that!!
I'm not the Vault Admin, so I don't know if there's a default setting that demands checkout when loading projects. At least three SEs have experienced the same issue.
Any ideas on what could be the problem??
Thanks!!
Using:
VS 2005 Team Suite C#
SQL Server 2005 SP3
Windos XP / Vista
Vault Client Version 5.04
Vault Server Version 5.0.4.18845
Vault 5.0 problem.
Moderator: SourceGear
Re: Vault 5.0 problem.
When you say the interfaces check out, do you mean project or solution files, or regular code files as well?
Have a user perform a Diff on one of the files that checks out automatically when opening. Are there any differences?
Have a user perform a Diff on one of the files that checks out automatically when opening. Are there any differences?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 5.0 problem.
only the project files are checked out, the code files are not. No differences between the local file and the server file for the file that is trying to check out.Beth wrote:When you say the interfaces check out, do you mean project or solution files, or regular code files as well?
Have a user perform a Diff on one of the files that checks out automatically when opening. Are there any differences?
I'm still researching...
Re: Vault 5.0 problem.
One thing that might possibly cause that would be the project being shared amongst different solution files. Recently we had a user whose project GUIDs kept changing because of that: http://support.sourcegear.com/viewtopic ... UID#p58532.
Or maybe the file stamp was updated by a one of the times it was opened one way. You could try turning on to check for changes using CRCs to see if it happens under that option as well. That is found in the Vault Tools - Options - Local Files.
Or maybe the file stamp was updated by a one of the times it was opened one way. You could try turning on to check for changes using CRCs to see if it happens under that option as well. That is found in the Vault Tools - Options - Local Files.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support