I really want this merge tool to work inside of Visual Studio 2012. I live in Visual Studio all day long...and if merging can become better via calls to the TFS Build process for gated check-ins, I'd use this tool in a heart beat and sign it's high praises to every developer i meet.

There's a few common formatting changes that can be made to XAML documents without affecting the semantics but that do affect traditional merge tools quite badly. It would be great not to have to deal with those by hand.

The most common changes are probably reordering element attributes, and moving attributes onto separate lines vs. having > 1 attribute on the same line.

There is then the equivalent issue to what you have been talking about already: re-ordering and re-arranging elements in the file. Note that XAML has an extra way of associating the elements in two versions of a file in the "x:Uid" attribute, which is used for maintaining localisation in the face of file re-ordering.

It would be great to have XAML support.

There's a few common formatting changes that can be made to XAML documents without affecting the semantics but that do affect traditional merge tools quite badly. It would be great not to have to deal with those by hand.

The most common changes are probably reordering element attributes, and moving attributes onto separate lines vs. having > 1 attribute on the same line.

There is then the equivalent issue to what you have been talking about already: re-ordering and re-arranging elements in the file. Note that XAML has an extra way of…

Right now the samples on the website about splitting up a class are a bit unrealistic since they all include splitting the class up but keeping it all in the same file. In reality, we often move code to different files and still want to merge. SemanticMerge will be revolutionary if it can solve this problem.

For strongly typed languages like Haskell (and probably for some others too) it would make sense to have the ability to check the merge result with the compiler or some other external tool and to fall back on a manual merge if it does not compile.

I want to merge each file in a directory (i.e. for different branches of the same code). I should be able to choose the files that I want to merge with filters (i.e. only source files, not images, etc).

You could use this tool to generate a commit message template in a little text box, and optionally copied to the user's clipboard, for example \samples\FileCache\samplesemanticmergetool.bat would generate: