This document covers the different components that make up a .NET Core distribution and how they are versioned. This document currently covers the 1.x releases.
How components in .NET Core are versioned.
.NET Core consists of multiple components that are each versioned independently and can often be mixed and matched.
Shared Framework. This contains the APIs and the Virtual Machine and other runtime services needed for running .NET Core applications.
The current .NET Core Virtual Machine is called CoreCLR. This executes the .NET bytecode by compiling it JIT and provides various runtime services including a garbage collector. The complete source code for CoreCLR is available at https://github.com/dotnet/coreclr.
The .NET Core standard APIs are implemented in CoreFX. This
provides implementations of all your favourite APIs such as
System.Theading and so on. The source code for
CoreFX is available at https://github.com/dotnet/corefx.
Host is also called the muxer or driver. This components
dotnet command and is responsible for deciding what
happens next. The source for this is available at
SDK is also sometimes called the CLI. It consists of the
various tools (
dotnet subcommands) and their implementations that
deal with building code. This includes handling the restoring of
dependencies, compiling code, building binaries, producing packages
and publishing standalone or framework dependent packages. The SDK
itself consists of the CLI, which handles command line operations
(at https://github.com/dotnet/cli) and various subprojects that
implement the various operations the CLI needs to do.
Various official and unoffical packages, tarballs, zips and installers for .NET Core (including those available on https://dot.net/core) provide .NET Core in many variants. Two common ones are SDKs and Runtimes.
Each SDK install or Runtime install contains a number (possibly 0) of hosts, sdk and shared framework components described above.
.NET Core Runtime contains
.NET Core SDK contains