It seems that Vault still gets confused on versions of the files and does not always retrieve the latest version of the file from the source code database. Even without the IDE integration (I have disabled the integration, I am using directly the Vault client). It looks like a Vault bug.
One other issue I encountered several times, if you want to make sure your latest version of code makes to the repository, you have to completely check the code-in, then check-it out if you want to keep working on it.
Does Vault Client 2.0.3 address these problems?
Latest version of file from Vault DB?
Moderator: SourceGear
-
- Posts: 5
- Joined: Fri May 21, 2004 12:28 pm
- Location: Toronto
- Contact:
By default, Vault will not overwrite a file if it has been modified by the user. If the status of the file is edited or renegade, you have to choose the "Overwrite" option in the Get Latest dialog.
See http://support.sourcegear.com/viewtopic.php?t=782 for a discussion of some of the common reasons why files don't get overwritten after a Get.
Also see
http://support.sourcegear.com/viewtopic.php?t=162 and
http://support.sourcegear.com/viewtopic.php?t=131
for additional information about Get options and file status.
Also, there is a "Keep Checked out" checkbox in the GUI client checkin dialog to keep the file checked out after checking it in. Visual Studio has its own option that controls this behavior in Visual Studio.
See http://support.sourcegear.com/viewtopic.php?t=782 for a discussion of some of the common reasons why files don't get overwritten after a Get.
Also see
http://support.sourcegear.com/viewtopic.php?t=162 and
http://support.sourcegear.com/viewtopic.php?t=131
for additional information about Get options and file status.
Also, there is a "Keep Checked out" checkbox in the GUI client checkin dialog to keep the file checked out after checking it in. Visual Studio has its own option that controls this behavior in Visual Studio.