.NET Framework, Core, and Standard

One of the things that confuses people the most when talking about .NET is understanding the different types of .NET that exist.

For a slightly longer version, check out the entry on “History of C#.” But in summary, .NET was originally .NET Framework.

At some point, Microsoft decided to get “creative” 🤡 and split .NET into parts to make it cross-platform. This complicated things quite a bit, so they unified it back into .NET (just that).

Let’s take a closer look at them 👇.

.NET Framework

.NET Framework is the original implementation of .NET released by Microsoft in 2002, primarily for developing desktop and web applications on Windows.

The implementation of .NET Framework includes a virtual machine, the CLR, which runs applications in a controlled execution environment.

Additionally, it includes a large number of libraries, data access (ADO.NET), web services (WCF), web application development (ASP.NET), and desktop applications (WinForms, WPF).

.NET Framework is designed exclusively for Windows, which means that applications developed with it cannot run natively on other operating systems.

.NET Core and Standard

This is where Microsoft aims to enhance .NET to make it cross-platform. Basically, the idea was that there are “many things” that are done the same across all platforms.

For example, a library that performs mathematical functions will run the same across all platforms. So all those libraries can be “taken out” to a common area, which we call .NET Standard.

Things that depend on the Operating System (for example, how to manage files) are what finish the implementation. And these are referred to as “Core”.

.NET Core

.NET Core is a cross-platform and open-source version of the .NET ecosystem, first released in 2016. It was designed to replace .NET Framework.

The main idea behind .NET Core was to be able to run on multiple operating systems. Thus, you could have your same app on Windows, Linux, Mac, iOS, Android, etc.

Being open-source, it allows the community to contribute to and improve the platform, and its updates can be viewed and audited directly on GitHub.

.NET Standard

.NET Standard is not a platform or implementation (like .NET Framework or .NET Core), but an API specification. In other words, .NET Standard defines a set of APIs that any .NET implementation must comply with.

Its goal is to provide a way to create class libraries that can run on multiple .NET platforms without needing to be rewritten for each one.

Did that go well the first time? I can tell you that it didn’t. Because there are also different versions of .NET Standard. Here’s a summary of the compatibility of each one.

.NET

As I said before, the previous “didn’t go so well.” So it was decided to reunify it into .NET (just that). Since version .NET 5 and successive versions, the .NET ecosystem has been unified into a single platform.