Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About johndog

  • Rank
  1. I had a situation where a large file had a class with many methods in it. In one branch these methods were changed slightly, and in another the methods were extracted into new class and .cs file. When these branches were merged, SemanticMerge simply presented this as a conflict with a "change" on their side, and a "delete" on your side, and seemed to ignore the fact that the same methods existed in another added file, so it should have represented a move, not a delete. Is there a trick to having SemanticMerge analyze the whole change for moves between files?