Semantic handles the “using” references automatically.: The conflict in the using area is automatically solved by SemanticMerge.

Scenario definition: Two “using” methods added in different places,

SemanticMerge detects the added code: SemanticMerge is able to detect that the code is the same, even when it was added from different locations.

Scenario definition: The same method added by two developers on two different versions and in different places.

Visual Merge explaining the scenario: Visual Merge helps understanding the scenario and how the code was refactored.

Conflict solved: The developer can click on the merge button to solve the method conflict.

SemanticMerge detects the method conflict: Even when the method has been moved by one contributor, SemanticMerge clearly detects the conflict.