I have been upgrading a few projects from their original PCL profiles (now
deemed obsolete) to the Net Standard platform specification. It turned out
to be a relatively straightforward process, but it does have its small hurdles,
especially so if in the meantime you also want to transition to the new,
.csproj format as the migration will leave you with a now
project.json project. In this article, I will cover upgrading
a project from Portable Class Library to NetStandard. In a follow-up post,
I plan to write about the switch from
project.json to the new
So let us take the Eve.NET project as an example. It makes a good candidate because it is an open source project, so you can go and have a look at the source code before and after the switch from PCL to NetStandard.
The first step was, of course, opening the project in Visual Studio 2017. If you are on an older VS version, you should upgrade. For many valid reasons indeed, among them the fact that Visual Studio 2017 comes with a built-in option to switch a project to NetStandard.
As you can see, before the upgrade Eve.NET was a Profile259 PCL project. As metioned, Visual Studio offers the option to switch to the .NET Platform Standard. By clicking the link, you get a fair warning that you might not be able to use the same APIs when targeting NetStandard. That makes sense because, as you probably know already, NetStandard is an API specification while a PCL essentially is the intersection (or lowest common denominator) of the APIs available on target platforms. PCL compatibility has never been the design goal of NetStandard.
Generally speaking, NetStandard offers a wider range of APIs compared to most PCL profiles and, most importantly, is planned to go through a cycle of incremental upgrades of the API specification, each one denoted by a version number. We already went from 1.0 to 1.6, with 2.0 currently being developed. NetStandard 2 will be a significant milestone, just give a look at the impressive diff between 1.6 and 2.0. A lot of open source projects are eagerly waiting on NetStandard 2 release (Q3 2017).
Upon confirming the switch, you might get the following show-stopper (I did):
This dialog will pop up if your project never has opted-in for NuGet 3.0. If this is the case, you have to go back, uninstall all NuGet packages, then attempt the switch again. When the migration is complete, you will have to re-install the packages, provided that they are compatible with NetStandard. In Eve.NET case the only dependency is Json.NET, which supports NetStandard 1.3, which also means that Eve cannot support previous NetStandard versions.
Now, if you give a look at the installed packages, you will find that you have
a couple of new entries:
NETStandard.Library, which is pretty
Microsoft.NETCore.Portable.Compatibility. This one will
only appear when you convert from a PCL: a brand new NetStandard project will
not take a dependency on it. If you are not using any legacy code, like NET
4.0-only, or Silverlight, you should be able to drop this dependency safely (I
did with no consequences).
The project is now NetStandard and ready to be used on all the platforms supporting your chosen version: NETCore, Windows, Xamarin, UWP, you name it.
However, you will soon notice that the project has gained a
file. It is ok, it works just fine, but it is obsolete: with Visual Studio 2017
project.json was abandoned for a new, streamlined and pretty darn powerful,
.csproj project file. In the next article, I will show you how to move your
project forward by dropping
project.json and embracing the new project type
(and other niceties, like dropping the
.nuspec file in the process).