| eng | ||
| resources/images | ||
| src | ||
| test | ||
| TestAssets | ||
| tools/sdk-readme-table-generator | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .vsts-ci.yml | ||
| build.cmd | ||
| build.sh | ||
| CODE-OF-CONDUCT.md | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| Downloads2.x.md | ||
| global.json | ||
| LICENSE | ||
| Microsoft.DotNet.Cli.sln | ||
| Native.sln | ||
| NuGet.config | ||
| PULL_REQUEST_TEMPLATE | ||
| README.md | ||
| run-build.ps1 | ||
| run-build.sh | ||
| SECURITY.md | ||
| source-build.slnf | ||
| THIRD-PARTY-NOTICES | ||
.NET Core SDK
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.
Looking for released versions of the .NET Core tooling?
Download released versions of the .NET Core tools (CLI, MSBuild and the new csproj) at https://dot.net/core.
Found an issue?
You can consult the Documents Index for the CLI 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.
Building
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.2.0.1 or later
- Install MSVC Build tools for x86/x64/arm64, v14.28-16.9
Build status
| All legs |
|---|
Installers and Binaries
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.
Example:
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>
Note: that you may need to add the dotnet5 feed for a short period of time while .NET transitions to .NET 6
For .NET 5 builds
<configuration>
<packageSources>
<add key="dotnet5" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet5/nuget/v3/index.json" />
</packageSources>
</configuration>
For .NET 3.1 builds
<configuration>
<packageSources>
<add key="dotnet3.1" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet3.1/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.
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
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 CLI repository.
License
By downloading the .zip you are agreeing to the terms in the project EULA.