CI to automate build of dotnet tarball for dotnet6-sdk aport https://gitlab.alpinelinux.org/alpine/aports/-/tree/master/community/dotnet6-sdk
Find a file
dotnet-maestro[bot] 7d53558cfe
Update dependencies from https://github.com/dotnet/sdk build 20210122.8 (#9517)
[master] Update dependencies from dotnet/sdk
2021-01-22 18:24:56 +00:00
eng Update dependencies from https://github.com/dotnet/sdk build 20210122.8 (#9517) 2021-01-22 18:24:56 +00:00
resources/images Publishes the binaries and native installers. 2018-12-19 16:08:49 -08:00
src Merge branch 'release/5.0.2xx' into master 2021-01-21 10:11:11 -08:00
test Revert "disable test as tool build for now" 2020-11-17 09:36:12 -08:00
TestAssets Update tests for .NET 6 2020-10-25 19:19:57 -07:00
tools/sdk-readme-table-generator Update README.md and table generator for linux-musl-arm 2020-12-15 12:57:44 +01:00
.editorconfig Checkin corefx editorconfig 2017-09-18 10:23:06 -07:00
.gitattributes Treat xlf as text 2017-12-07 16:00:07 -08:00
.gitignore Support setting "partition" for arcade to avoid conflicts of .dotnet and artifacts folders 2019-08-30 08:53:22 -07:00
.vsts-ci.yml [release/5.0.2xx] Enable linux-musl-arm* builds in CI 2020-12-13 17:28:29 +01:00
build.cmd Build script fixes for CI 2018-11-07 17:21:16 -08:00
build.sh Changes for core-sdk to move to yaml stages 2019-09-12 13:19:14 -07:00
CODE-OF-CONDUCT.md Link Code of Conduct 2020-04-02 13:48:35 -07:00
CONTRIBUTING.md Making this repo consume the dotnet-sdk-internal zip and produce a full core-sdk by using sdk-internal, runtime, lzma, templates and store. Also deleted a bunch of now, unecessary code. I am sure there is more to be deleted though. 2017-10-13 10:45:50 -07:00
Directory.Build.props Update the installer target framework net6.0 (#9069) 2020-11-13 10:56:11 -08:00
Directory.Build.targets [master] Update dependencies from dotnet/sdk (#9172) 2020-12-23 14:53:41 +00:00
Downloads2.x.md Fix download links 2020-02-28 15:22:23 -08:00
global.json Update dependencies from https://github.com/dotnet/arcade build 20210119.2 (#9507) 2021-01-21 13:53:31 +00:00
LICENSE [master] Update dependencies from dotnet/arcade (#1056) 2019-03-20 21:42:05 +00:00
Microsoft.DotNet.Cli.sln Use Task to calculate template versions 2020-01-25 16:40:47 -08:00
NuGet.config [master] Update dependencies from dotnet/sdk (#9512) 2021-01-22 02:11:48 +00:00
PULL_REQUEST_TEMPLATE Update pull request template (#7288) 2020-04-24 11:06:59 -07:00
README.md Update README.md and table generator for linux-musl-arm 2020-12-15 12:57:44 +01:00
run-build.ps1 Workaround arcade bug with AllowEmptySignList 2019-01-11 14:57:14 -08:00
run-build.sh Don't set CONFIGURATION environment variable (as this by default flows to tests) 2018-11-08 12:51:27 -08:00
SECURITY.md Add SECURITY.md 2020-02-26 01:44:53 +00:00
THIRD-PARTY-NOTICES Add license text to LZMA SDK license notice 2017-02-26 12:11:05 -08:00

.NET Core SDK

Join the chat at https://gitter.im/dotnet/cli GitHub release GitHub repo size GitHub issues-closed GitHub contributors

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.

Build status

All legs
Build Status

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/master/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.

Platform Master
(6.0.x Runtime)
Release/5.0.2XX
(5.0 Runtime)
5.0.100 RTM
(5.0 Runtime)
Release/3.1.4XX
(3.1.x Runtime)
Release/3.1.1XX
(3.1.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
zip - Checksum

zip - Checksum
Windows arm64
zip

Installer - Checksum
zip

Installer - Checksum
zip
N/A N/A
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
N/A N/A N/A N/A
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
N/A N/A N/A
Linux-musl-arm64
tar.gz - Checksum

tar.gz - Checksum
N/A N/A N/A
RHEL 6 N/A N/A N/A
tar.gz - Checksum

tar.gz - Checksum

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.