Take a deep look into the next diff: that's right, one method was moved to a new class and changed at the same time. Plastic acknowledges that and shows the diffs semantically. Note how deleted "usings" are also correctly identified.
Check the second example: Even when two methods are moved and then changed, Plastic tracks them correctly to calculate the diff. We apply our SemanticMerge tech here, and this is just the first step towards semantic version control.
The integrated semantic diff also adds an outline on the left to quickly navigate and highlight changes.
And a “visual diff” helps you understanding complex refactor at first glance:
Refactor Analysis adds multi-file semantic diff capabilities – what if you decide to split a class in two and move one of them to another file? The new “analyze refactors” in Plastic SCM can easily track it.
Take a careful look at the example below: the old Socket class was split in two. The “Listen()” method was moved to the new ServerSocket.cs file and Plastic can track it and show you how it was changed!
Refactoring is key to keep code quality high and now diffing the refactored code will be straightforward.
As you can see, Refactor Analysis or multi-file semantic diff is a huge step ahead in what the version control can do and how it can help you being more productive on a daily basis. We think that what you see here today will be the standard in a few years.
Check the next screenshot to see how the regular file diff is decorated with new icons to explain that a “cross-file diff” has been detected.
Semantic Method History – ever wanted to see the history of a method? Yes, a method, not a file. Even if the method was renamed or moved inside the file...
The next screenshot shows the "visual diff" in action explaining the change done above:
the "Send()" method was moved down as you clearly see inside Visual Studio.
Visit our Gallery to learn more about the integration with Visual Studio
Merge refactored code – rename files, move them to different directories, and merge them effortlessly. Plastic is all about branching and merging. Learn more about what Plastic merge can do.
Work in task branches – the key concept we built Plastic around.
Work distributed – Plastic is a full featured distributed version control system. Heard of Git, right? Well, think of Plastic as a Git on steroids plus great GUIs and Semantic.