The .NET SDK 5.0.206 release is available for download. The latest 5.0 release is always listed at .NET 5.0 Releases.
| SDK Installer1 | SDK Binaries1 | Runtime Installer | Runtime Binaries | ASP.NET Core Runtime | Windows Desktop Runtime | |
|---|---|---|---|---|---|---|
| Windows | x86 | x64 | Arm64 | x86 | x64 | Arm64 | x86 | x64 | Arm64 | x86 | x64 | Arm64 | x86 | x64 | Hosting Bundle2 |
x86 | x64 | Arm64 |
| macOS | x64 | x64 | x64 | x64 | x64 | - |
| Linux | Snap and Package Manager | x64 | Arm | Arm64 | x64 Alpine | Packages (x64) | x64 | Arm | Arm64 | Arm64 Alpine | x64 Alpine | x641 | Arm1 | Arm641 | x64 Alpine | - |
| Checksums | Checksums | Checksums | Checksums | Checksums | Checksums |
- Includes the .NET Runtime and ASP.NET Core Runtime
- For hosting stand-alone apps on Windows Servers. Includes the ASP.NET Core Module for IIS and can be installed separately on servers without installing .NET Runtime.
The .NET SDK includes a matching updated .NET Runtime. Downloading the Runtime or ASP.NET Core packages is not needed when installing the SDK.
You can check your .NET SDK version by running the following command. The example version shown is for this release.
$ dotnet --version
5.0.206Visit .NET Documentation to learn about .NET, for building many different types of applications.
The .NET Docker images have been updated for this release. The .NET Docker samples show various ways to use .NET and Docker together. You can use the following command to try running the latest .NET 5.0 release in containers:
docker run --rm mcr.microsoft.com/dotnet/samplesThe following repos have been updated.
- dotnet/sdk: .NET SDK
- dotnet/aspnet: ASP.NET Core Runtime
- dotnet/runtime: .NET Runtime
- dotnet/runtime-deps: .NET Runtime Dependencies
- dotnet/samples: .NET Samples
You need Visual Studio 16.10 or later to use .NET 5.0 on Windows. On macOS, you need the latest version of Visual Studio for Mac. The C# extension for Visual Studio Code supports .NET 5.0 and C# 9.
Your feedback is important and appreciated. We've created an issue at dotnet/core #6553 for your questions and comments.