Delete / Rename Conflict

[BradleyUffner]

Currently using Vault 5.0.1 with Visual Studio Pro 2008 on Windows 7 x64.

Create a new VB Windows Forms project.
Add a new form Called Form1.
Add a new form called Form2.
Check everything into vault.

Delete Form1.
Rename Form2 to Form1.
Try to check in to vault and it freaks out with many errors, leaving the pending operations in strange states that are very tricky to fix.

I've had this happen to me several times over the past few months when I forget to check in the delete before doing the rename.

[lbauer]

I followed you steps and see what you mean. I'll check with our developers to see if commiting the Delete is the only way to handle this.

[lbauer]

We've logged bug 14900 to fix this in a future release.

In the mean time, there are two workarounds: commit the delete first or do these operations in the GUI client.

Thanks for the report.

[BradleyUffner]

Just wanted to let you know, that in the workaround of checking in between the delete and rename, when another user does Get Latest after the whole operation is checked in the renamed file will show up as renegade on thier machine.

[Beth]

In the Vault - Tools - Options - Local Files, what do they have set for 'Perform Repository Deletions Locally?'

[BradleyUffner]

"Remove working copy only if unmodified"

[Beth]

Do your users share working folders by any chance?

If not, it might be time for me to take a more direct look. I can't seem to reproduce the renegade status your other users receive. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?