Visual Studio Code is a nice little editor by Microsoft that is incredibly popular at the moment. StackOverflow 2019 survey ranked it as the most used code editor: more than half the respondents claimed to use it! Besides, it has a really active community and boasts a powerful set of extensibility options.

We use it here at Códice Software, too. Our websites, the Plastic SCM Server WebUI, some client plugins... All those are often modified and extended using Visual Studio Code.

So, one day we asked ourselves, 'Wouldn't it be nice to have Plastic SCM information embedded in this wonderful editor?' That was the event that triggered the birth of the Plastic SCM extension for VS Code.

Extension overview

Let us share how to create a minimalist Microsoft Windows installation to host our new .net Core Plastic SCM Server. Didn't you know we run on .net core? Check this blogpost.

What is Windows Server Core?

Windows Server Core is a minimal installation option that is available when you are deploying a regular Windows Server. It includes most but not all server roles, which makes the disk footprint around 3-5GB.

With Server Core, Microsoft stripped away the graphical user interface, so you must run all the operations using the command line. Not a problem for a server-side environment.

You can always install Windows Core Server in your office using a small machine, but as it requires a small number of resources, it is perfect for hosting it at Amazon.

You can now hook web triggers to Plastic SCM operations. It has been a reality for years on the on-premises Plastic SCM Server, but now Plastic Cloud also supports it!

Do you remember we recently released cloud2? Web triggers is one of the new features in the new Cloud. Stay tuned because there's much more to come 🙂

What a web trigger is?

Somebody introduced a bug in the codebase, as a failing test demonstrates. But the test is the symptom, and the cause might be too deep to know exactly where it is.

It would help a lot if you were able to pinpoint the changeset where the bug was introduced, but that's manual labor. You must first switch your workspace to a changeset, then build the necessary assemblies, then pass the specific test, and based on the result, decide which is the next changeset to test. That's an awful lot of steps!

That's where bisect is useful, and that's what I bring you today.

Let's bisect a Plastic SCM repository using PowerShell!

We just launched our new Plastic Cloud, code-named cloud2. New users can evaluate and purchase this new offering, while we will migrate all current customers from cloud1 to cloud2.

The new cloud2:

  • It's incredibly fast. Better servers, more efficient, and intensive memory use and caching, and much faster metadata storage and improved data transfer.
  • Dramatically reduces latency. More metadata servers mean you are closer to your data.
  • Enables long-awaited features. Access shelves in the Cloud, move changesets to other branches, use cloud triggers, and much more. We have a very solid foundation for feature parity with on-prem servers.
UPDATE March 17, 2020: You can now read a summary about what were the main features launched during Plastic 8.0.

As every year, we jump to a new number, 9.0 this time. For all of you using subscriptions, it will be transparent.

UPDATE March 10, 2020: Edited the Install on macOS from tar.gz section. We updated the instructions for installing the Plastic SCM server .Net Core on macOS.
UPDATE March 2, 2020: We edited the Current limitations section because the Plastic SCM .NET Core Server includes WebAdmin, WebUI, and DevOps (mergebots) since release

Great news! We just published the Plastic SCM server built on .NET Core, the cross-platform, rock-solid, super-fast and officially supported framework.

The new servers are available for Linux, macOS, and Windows beginning with version

The new servers are fully compatible with your current installation, but as of, they don't include WebAdmin, WebUI, and mergebots. We'll release a new version packaging these features soon. These features are available since version

The Linux servers are available as tar.gz and also regular packages.

Windows and macOS servers are only available as zip and tar.gz at this point. We'll make them full regular installers soon.