.NET SDK Installers

This repo contains the source code for the cross-platform .NET SDK. It aggregates the .NET toolchain, the .NET runtime, the templates, and the .NET Windows Desktop runtime. It produces zip, tarballs, and native packages for various supported platforms.

Looking for released versions of the .NET tooling?

The links below are for preview versions of .NET tooling. Prefer to use released versions of the .NET tools? Go to https://dot.net/download.

Looking for .NET Framework downloads?

.NET Framework is the product from which the .NET Core project originated. .NET Core (mostly just called ".NET" here) adds many features and improvements and supports many more platforms than .NET Framework. .NET Framework remains fully supported and you can find the downloads on the .NET website. For new projects, we recommend you use .NET Core.

Want to contribute or find out more about the .NET project?

This repo is for the installers. Most of the implementation is in other repos, such as the dotnet/runtime repo or the dotnet/aspnetcore repo and many others. We welcome you to join us there!

Found an issue?

You can consult the Documents Index for the SDK repo to find out current issues, see workarounds, and to see how to file new issues.

This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information, see the .NET Foundation Code of Conduct.

Build .NET installer

The repository contains native code project required for the Windows installer. If you intend to build it locally on Windows, you will need to ensure that you have the following items installed.

• Install CMAKE 3.21.0 is required if you're building VS 17.0. Make sure to add CMAKE to your PATH (the installer will prompt you).

• Install MSVC Build tools for x86/x64/arm64, v14.28-16.9

• build for basic build

• build -pack to build the installer

• To build in VS, run a command line build first, then run artifacts\core-sdk-build-env.bat from a VS command prompt and then devenv Microsoft.DotNet.Cli.sln

• To test different languages of the installer, run artifacts\packages\Debug\Shipping>dotnet-sdk-3.1.412-win-x64.exe /lang 1046 using the LCID of the language you want to test

Build .NET from source (source-build)

This repo also contains code to help you build the entire .NET product end-to-end from source (often referred to as source-build), even in disconnected/offline mode. Please see the dotnet/source-build repo for more information.

Support

.NET Source-Build is supported on the oldest available .NET SDK feature update for each major release, and on Linux only. For example, if .NET 6.0.1xx, 6.0.2xx, and 7.0.1xx feature updates are available from dotnet.microsoft.com, Source-Build will support 6.0.1xx and 7.0.1xx. For the latest information about Source-Build support for new .NET versions, please check our GitHub Discussions page for announcements.

Prerequisites

The dependencies for building .NET from source can be found here.

Building .NET 8.0

.NET 8.0 (currently in prerelease) and newer will be built from the dotnet/dotnet repo. Clone the dotnet/dotnet repo and check out the tag for the desired release. Then, follow the instructions in dotnet/dotnet's README to build .NET from source.

Codespaces

It is also possible to utilize GitHub Codespaces and build .NET from the dotnet/dotnet repository from source that way. You can either create a Codespace in dotnet/dotnet directly or you can also make one from a PR branch in dotnet/installer. This will give you an environment with the VMR checked out and containing all of new changes from the PR. This can be especially valuable for investigations of source-build failures during PRs.

To create a Codespace for a dotnet/installer PR, use the vmr-source-build devcontainer configuration (select this when "newing the Codespace with options" under the three-dots-menu). Further instructions on how to build inside of the Codespace will be available upon launch.

Building .NET 7.0 and .NET 6.0

1. Create a .NET source tarball.

   ./build.sh /p:ArcadeBuildTarball=true /p:TarballDir=/path/to/place/complete/dotnet/sources
   

   This fetches the complete .NET source code and creates a tarball at artifacts/packages/<Release|Debug>/Shipping/. The extracted source code is also placed at /path/to/place/complete/dotnet/sources. The source directory should be outside (and not somewhere under) the installer directory.

2. Prep the source to build on your distro. This downloads a .NET SDK and a number of .NET packages needed to build .NET from source.

   cd /path/to/complete/dotnet/sources
   ./prep.sh --bootstrap
   

3. Build the .NET SDK

   ./build.sh --clean-while-building
   

   This builds the entire .NET SDK from source. The resulting SDK is placed at artifacts/x64/Release/dotnet-sdk-7.0.100-your-RID.tar.gz.

   Optionally add the --online flag to add online NuGet restore sources to the build. This is useful for testing unsupported releases that don't yet build without downloading pre-built binaries from the internet.

   Run ./build.sh --help to see more information about supported build options.

4. (Optional) Unpack and install the .NET SDK

   mkdir -p $HOME/dotnet
   tar zxf artifacts/x64/Release/dotnet-sdk-7.0.100-your-RID.tar.gz -C $HOME/dotnet
   ln -s $HOME/dotnet/dotnet /usr/bin/dotnet
   

   To test your source-built SDK, run the following:

   dotnet --info
   

Build status

Visibility	All legs
Public
Microsoft Internal

Installers and Binaries

You can download the .NET SDK as either an installer (MSI, PKG) or a zip (zip, tar.gz). The .NET SDK contains both the .NET runtime and CLI tools.

Note: Be aware that the following installers are the latest bits. If you want to install the latest released versions, check out the preceding section. With development builds, internal NuGet feeds are necessary for some scenarios (for example, to acquire the runtime pack for self-contained apps). You can use the following NuGet.config to configure these feeds. See the following document Configuring NuGet behavior for more information on where to modify your NuGet.config to apply the changes.

For .NET 9 builds

<configuration>
  <packageSources>
    <add key="dotnet9" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json" />
  </packageSources>
</configuration>

For .NET 8 builds

<configuration>
  <packageSources>
    <add key="dotnet8" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json" />
  </packageSources>
</configuration>

For .NET 7 builds

<configuration>
  <packageSources>
    <add key="dotnet7" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7/nuget/v3/index.json" />
  </packageSources>
</configuration>

Do not directly edit the table below. Use https://github.com/dotnet/installer/tree/main/tools/sdk-readme-table-generator to help you generate it. Make sure to run the table generator test and make any changes to the generator along with your changes to the table. Daily servicing builds aren't shown here because they may contain upcoming security fixes. All public servicing builds can be downloaded at http://aka.ms/dotnet-download.

Table

---

Platform	main (9.0.x Runtime)	9.0.1xx-preview3 (9.0-preview3 Runtime)	8.0.4xx (8.0 Runtime)	8.0.3xx (8.0 Runtime)	Release/7.0.4xx (7.0.x Runtime)
Windows x64	Installer - Checksum zip - Checksum	Installer - Checksum zip - Checksum	Installer - Checksum zip - Checksum	Installer - Checksum zip - Checksum	Installer - Checksum zip - Checksum
Windows x86	Installer - Checksum zip - Checksum	Installer - Checksum zip - Checksum	Installer - Checksum zip - Checksum	Installer - Checksum zip - Checksum	Installer - Checksum zip - Checksum
Windows arm	N/A	N/A	N/A	N/A	N/A
Windows arm64	Installer - Checksum zip	Installer - Checksum zip	Installer - Checksum zip	Installer - Checksum zip	Installer - Checksum zip
macOS x64	Installer - Checksum tar.gz - Checksum	Installer - Checksum tar.gz - Checksum	Installer - Checksum tar.gz - Checksum	Installer - Checksum tar.gz - Checksum	Installer - Checksum tar.gz - Checksum
macOS arm64	Installer - Checksum tar.gz - Checksum	Installer - Checksum tar.gz - Checksum	Installer - Checksum tar.gz - Checksum	Installer - Checksum tar.gz - Checksum	Installer - Checksum tar.gz - Checksum
Linux x64	DEB Installer - Checksum RPM Installer - Checksum see installer note below1 tar.gz - Checksum	DEB Installer - Checksum RPM Installer - Checksum see installer note below1 tar.gz - Checksum	DEB Installer - Checksum RPM Installer - Checksum see installer note below1 tar.gz - Checksum	DEB Installer - Checksum RPM Installer - Checksum see installer note below1 tar.gz - Checksum	DEB Installer - Checksum RPM Installer - Checksum see installer note below1 tar.gz - Checksum
Linux arm	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum
Linux arm64	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum
Linux-musl-x64	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum
Linux-musl-arm	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum
Linux-musl-arm64	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum	tar.gz - Checksum
RHEL 6	N/A	N/A	N/A	N/A	N/A

Reference notes:

1: Our Debian packages are put together slightly differently than the other OS specific installers. Instead of combining everything, we have separate component packages that depend on each other. If you're installing the SDK from the .deb file (via dpkg or similar), then you'll need to install the corresponding dependencies first:

• Host, Host FX Resolver, and Shared Framework
• ASP.NET Core Shared Framework

.NET Core SDK 2.x downloads can be found at .NET Core SDK 2.x Installers and Binaries but they are out of support.

Looking for dotnet-install sources?

Sources for dotnet-install.sh and dotnet-install.ps1 are in the install-scripts repo.

Questions & Comments

For all feedback, use the Issues on the .NET SDK repository.

License

The .NET project uses the MIT license.

The LICENSE and ThirdPartyNotices in any downloaded archives are authoritative.