These are the steps we use to reproduce this problem:
File example.h has 10 versions.
1) Show History, pin version 9
2) Get Latest Version
3) File status shows up as Renegade. Using Get Latest Version again gives a prompt to Overwrite, no change after overwriting. The date of the local version is shown as 1 day earlier than the remote version.
Logs say that we successfully get the correct version, and if we Show Differences between the two "renegade" files, it says that there are no differences. We've tried this into an empty local folder, same problem.
What's strange is that only certain versions for certain files have this issue. Version 8 of the above file works just fine, while version 9 and 7 will show up as Renegade after following the above. File example2.h works just fine, while file example3.h has the above problem when using version 5/6. In all the problem cases, the local date is shown as being a day earlier than the remote date.
We're using Vault version 5.0.3.18802.
Get Latest Version creates Renegade files
Moderator: SourceGear
Re: Get Latest Version creates Renegade files
Are you performing the Get in Visual Studio, or are all your actions happening in the Vault GUI client?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support