You refactor some code before doing a bug fix, you clean it up to better understand how it works, and leave the code in a better status than you found it, in purest boy-scout style :P.

Then you move methods to a new class in a new file. And later make some modifications to the moved methods. Easy, uh?

Well, Plastic SCM can now track the refactor and diff it correctly, because we have just implemented multi-file semantic diff or "analyze refactors":

This is another step forward towards semantic version control as we explained about one month ago with our initial release.

Now Plastic can track moved code across files, and soon we'll apply the same tech to merging.

The new release we’re announcing today, BL677, includes a feature that pretty much explains what our vision for the future is: semantic version control.

It may sound like big words but it is a pretty simple concept: the version control “understands” the code. So when you diff C#, Java code, C, VB.net (and hopefully all languages in the near future), it knows how to handle it:

The Windows GUI in release 674 is out and it comes with a greatly improved diff system!!!

The new diff is based on a totally new text editor. It took us a while to complete the change but we believe the results are really worth. We received many requests and suggestions to improve the editors, so we’re very happy to finally release the new features.

The new text editor introduces a completely reworked syntax highlight, much faster handling of big files plus the ability to outline code to collapse methods, undo and many more!

Jenkins is an awesome open-source continuous integration (CI) tool built in Java and based on the Hudson project. The best feature of Jenkins is the ability to extend it using plugins that enable you to integrate it with different build systems such as MSBuild or MSTest.

In this article we will show you how to install and configure a Jenkins server with MSBuild and how to integrate it with Plastic SCM so that each of your commits will trigger builds in Jenkins.

This blog post introduces a few hints about what you can expect when you diff changesets (commits) in your version control. Something similar to what we wrote to explain the difference between 2-way and 3-way merge months ago.

The diff function

Diff (9) actually means “diff with previous” or Diff(8, 9). We’ll assume the Diff function to be Diff(src, dst).

In January of this year Microsoft made public their most innovative and disruptive product in quite some time called HoloLens, an augmented reality headset that combines breakthrough hardware, input and machine learning so that you can bring mixed reality experiences to life using the real world as your canvas. These are not just transparent screens placed in the center of a room with an image projected on them but truly immersive holograms that enable you to interact with the real world. This is a truly innovative product with a rich set of APIs that enable you to develop Windows Holographic applications that will blur the line between the real world and the virtual world.

As impressive as this may sound, Microsoft has been very quiet about this technology; only allowing a few videos and bits of information to be released. But at the most recent Microsoft Developer Conference//Build 2015, they allowed a select group of people, around 180 people in total including me, to try out this new technology.

On November 2014 Microsoft announced their new strategy for the .NET future. The most important part of the announcement was the release of .NET Core 5 as a componentized framework that will be shipped via NuGet. The .NET Core CLR is open source, and supports Windows, Linux and Mac OS X. It's publicly available in GitHub.