We’re glad to announce a new release of SemanticMerge today: 0.9.21.
This new build is very special because we’re adding a new language: Visual Basic .net!!
So now SemanticMerge is able to deal with two languages C# and VB.net and more are coming.
New examples availableAll the possible merge cases supported for C# are now ready for VB.net and in fact if you go to the “samples” subdirectory you’ll find a new collection of test cases ready to be tested just by “double clicking”:
And we added a couple of script files inside each example folder so you can directly double click and run. “samplesemanticmergetool” runs the semantic merge and “samplemergetool” runs the text based one so you can compare and see why “semantic” rocks :-)
A Visual Basic merge scenarioLook at the following scenario with concurrent changes made on a method that is also moved “divergently”:
This scenario will be hell for conventional text based merge tools but check how it looks like inside SemanticMerge.
Once the conflicts are solved, you can jump and rearrange the file too.
WebinarRemember we run a webinar this week and you can access the video here:
DownloadSemanticMerge beta is free so go to www.semanticmerge.com and grab a copy!
More new features on 0.9.21Together with the support of Visual Basic .net this new release include the following improvements:
- Redesigned (and improved) “merge info” panel. It now displays all the available information (if specified by the invoker of the tool) such us the contributor paths, the symbolic names (aliases you can use from the scm), owner, branch information, changeset and comment (if sent by the scm).
- The unmatch button was not able to deal with “moves out of scope” which means “methods (or any other element) move from one class to a different one (one container to another)”. It is now able to deal with it. It means that if the tool wrongly detected a move, you can unmatch and match again with the right one.
- Added a “diff button” for the “added-added” conflicts so that you can now compare the two contributors directly which is very useful (especially if you’re not using an external 2-way merge text-based tool).
- SemanticDiff now accepts symbolic names, which means you can send meaningful info from the scm (instead of the temporary files the scm will use for diffing and so on).
- The update window has been improved so starting on the next upgrade whenever an update is detected it will show the current version number, the one to be updated to, release notes (finally!) and even a link to the new installer (just in case you want to run a full installation).