Difference between .Net Core, Portable, Standard, Compact, UWP, and PCL?

by

I’ll answer your second question first:

I have a library that targets .Net 2.0, .Net 4.5, and UWP. Targeting UWP required creating a new VS project and linking all the existing files, which is a huge pain. Now someone is telling me it doesn’t work for PCL, and from the sound of it I have to do it AGAIN for .Net Standard!?)

If I want to write a library that’s usable to as large an audience as possible, which one (or more than one) of these do I need to use?

Short answer: you should target netstandard. Use the lowest version that has all the APIs you need. You can use a tool like API Port to check your existing project for compatibility with a given netstandard version.

Unfortunately, this approach will leave behind older platforms, in your case, .NET 2.0. If maintaining .NET 2.0 support is necessary, then you’ll need a separate project (with linked files) to build a separate .NET 2.0 assembly.

On to the details…

What’s the difference!?

  • .Net Standard (netstandard) – this is the new cross-platform BCL API. It’s a “standard” in the sense that it’s just an API definition and not an implementation. The idea is that you can compile your library to (a version of) this API and it will run on any platform that supports that version.
  • .Net Core – you can think of this as a reference implementation of netstandard (with a few extra bits). It is a cross-platform implementation of that API. It is possible that UIs and other frameworks may build on it, but for now its only sure foothold is acting as the platform of choice for ASP.NET Core. [Side note: for historical reasons, “.NET Core” is completely different than the netcore NuGet target; when you’re in a NuGet context, netcore means “Windows 8/8.1/10”].
  • .Net Portable and Portable Class Libraries – Portable Class Libraries (PCLs) are a least-common-denominator approach to providing a cross-platform API. They cover a wide range of target platforms, but they are incomplete and not future-proof. They have essentially been replaced by netstandard.
  • .Net Compact – This is a completely different .NET framework with its own unique API. It is completely incompatible with any other framework, PCL, or netstandard version; as such, it is much more difficult to support than any other platform. However, it is still used on devices with tight memory constraints.
  • Universal Windows Platform – This was a Win10-era merging of the API between Windows Phone and desktop, allowing Windows Store apps/libraries to be written for both platforms. This has essentially been replaced by netstandard.

More Related Contents:

  1. What are the correct version numbers for C#?
  2. How should I inject a DbContext instance into an IHostedService?
  3. dotnet core System.Text.Json unescape unicode string
  4. Add client certificate to .NET Core HttpClient
  5. System.Text.Json: How do I specify a custom name for an enum value?
  6. What replaces WCF in .Net Core?
  7. How to load assemblies located in a folder in .NET Core console app
  8. Should I take ILogger, ILogger, ILoggerFactory or ILoggerProvider for a library?
  9. Using Razor outside of MVC in .NET Core
  10. Is there a way to make a console application run using only a single file in .NET Core?
  11. .NET Core and System.Drawing
  12. How to consume a Scoped service from a Singleton?
  13. Could not load file or assembly Microsoft.Extensions.DependencyInjection.Abstractions, Version=1.1.0.0
  14. Proper way to start and fire-and-forget asynchronous calls?
  15. .NET Core vs Mono
  16. Get List element position in c# using LINQ
  17. File permissions on Linux/Unix with .NET Core
  18. How do I reference a .NET Framework project in a .NET Core project?
  19. System.ServiceModel not found in .NET Core project
  20. Net Core: Execute All Dependency Injection in Xunit Test for AppService, Repository, etc
  21. Tips for optimizing C#/.NET programs [closed]
  22. Deserializing XML to Objects in C#
  23. EF Linq Error after change from dotnet Core 2.2.6 to 3.0.0
  24. MS Dynamics CRM online 2011 – Authentication issues
  25. Check if a property exists in a class
  26. Why we need Properties in C#
  27. Linq Query Group By and Selecting First Items
  28. Is .NET 4.0 Compatible with Windows XP SP2 or below? [closed]
  29. Why is WebBrowser_DocumentCompleted() firing twice?
  30. how do i get TcpListener to accept multiple connections and work with each one individually?

Leave a Comment