Unable to compare files when a Gap + Name Conflict occurs.
Accepted answer
A couple of workarounds you can use:
If the evil twin is in your workspace, and the incoming evil twin is in your team stream:
- Suspend the change set(s) that created your evil twin
- Accept the incoming changes
- Resume your suspended change sets, which will pop up the usual process for resolving evil twins, and use the editor to keep the changes that you want from the respective evil twins.
If the evil twin is in some location other than your team stream:
- Create a patch of the change set from the evil twin that you want applied
- Apply that patch to your workspace.
I've also submitted work item Extend the gap-merging wizard to handle incoming changes from an evil twin. (316860) to request the gap-merging wizard be enhanced to handle this case.
Comments
Thanks Geoffrey. I´ll subscribe to the work item.
Leonardo, both you and Geoffrey are correct. The Gap editor does not yet support merging the "(Name Conflict)" cases, or viewing the two different files in a compare editor. The only options are to either ignore the change and keep what is on disk, or to overwrite the existing file with the proposed file.
As you mentioned, the article does indicate that a two way compare would be possible, however it is not. I will update the article to correct this.
On top of what Geoffrey already mentioned about workarounds; if the user needs to see the content changes from the source change set, they can open up the source change set in the Change Explorer, and double click on the file representing the 'evil twin' (Note: As a convenience, at the top of the editor there is a "Source Change Set" hyperlink that will open the source change set in the Change Explorer).
1 vote