This repo contains the source code for the cross-platform .NET Core SDK. It aggregates the .NET Toolchain, the .NET Core runtime, the templates, and the .NET Core Windows Desktop runtime. It produces zip, tarballs, and native packages for various supported platforms.
Download released versions of the .NET Core tools (CLI, MSBuild and the new csproj) at https://dot.net/core.
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.
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
-
buildfor basic build -
build -packto build the installer -
To build in VS, run a command line build first, then run
artifacts\core-sdk-build-env.batfrom a VS command prompt and thendevenv 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 1046using the LCID of the language you want to test
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.
.NET Source-Build is supported on the oldest available .NET SDK feature update, and on Linux only. For example, if both .NET 6.0.1XX and 6.0.2XX feature updates are available from dotnet.microsoft.com, Source-Build will only support 6.0.1XX. For the latest information about Source-Build support for new .NET versions, please check our GitHub Discussions page for announcements.
The dependencies for building .NET from source can be found here.
-
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. -
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.shOn arm64, please use
./prep.sh --bootstrapinstead. This issue is being tracked here. -
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-6.0.100-fedora.33-x64.tar.gz.Optionally add the
--onlineflag 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 --helpto see more information about supported build options. -
(Optional) Unpack and install the .NET SDK
mkdir -p $HOME/dotnet tar zxf artifacts/x64/Release/dotnet-sdk-6.0.100-fedora.33-x64.tar.gz -C $HOME/dotnet ln -s $HOME/dotnet/dotnet /usr/bin/dotnet
To test your source-built SDK, run the following:
dotnet --info
| Visibility | All legs |
|---|---|
| Public | |
| Microsoft Internal |
You can download the .NET Core SDK as either an installer (MSI, PKG) or a zip (zip, tar.gz). The .NET Core SDK contains both the .NET Core 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 7 builds
<configuration>
<packageSources>
<add key="dotnet7" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7/nuget/v3/index.json" />
</packageSources>
</configuration>
For .NET 6 builds
<configuration>
<packageSources>
<add key="dotnet6" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json" />
</packageSources>
</configuration>
For .NET 6 Optional workloads The below feed is needed for 6.0 releases before RC1
We strongly recommend using --skip-manifest-update with dotnet workload install as otherwise you could pick up a random build of various workloads as we'll automatically update to the newest one available on the feed.
<configuration>
<packageSources>
<add key="maui" value="https://pkgs.dev.azure.com/azure-public/vside/_packaging/xamarin-impl/nuget/v3/index.json" />
</packageSources>
</configuration>
Please 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 have been removed as all servicing is done in private repos to avoid disclosure of critical security fixes. All public servicing builds can be downloaded at http://aka.ms/dotnet-download.
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:
.NET Core SDK 2.x downloads can be found here: .NET Core SDK 2.x Installers and Binaries
Sources for dotnet-install.sh and dotnet-install.ps1 are in the install-scripts repo.
For all feedback, use the Issues on the .NET CLI repository.
By downloading the .zip you are agreeing to the terms in the project EULA.