Get latest overwrites/modifies checked out files?

JPrime · Post by **JPrime** » Mon Jan 24, 2005 6:57 pm

When I do a get latest, Vault seems to want to overwrite or merge files I have checked out...shouldn't it just ignore those?

Post by **jclausius** » Mon Jan 24, 2005 9:41 pm

No, not necessarily.

There are useful instances when Getting over a checked-out file is desired:

1) When I want to overwrite my changes ( "When Code Goes Bad!" ), but not re-issue the lock.

2) Also, if someone modified an edited, checked-out file, in order not to "stomp" on other people's work, you will want to merge their changes into your file before checking the file back in. Assuming no conflicts in the changes of the file, this is can be done with a Get Latest -> Auto merge

JPrime · Post by **JPrime** » Mon Jan 24, 2005 10:03 pm

The problem we're having (I think) is in VS.Net, we get messages saying that the automerge failed when doing a get latest...is there any way to force a get latest to ignore checked out files?

Post by **jclausius** » Mon Jan 24, 2005 10:16 pm

Unfortunately, that functionality does not exist.

There is an Enhancement Request logged for this feature. I've added your name to the list of people asking for this feature.