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] 2f78f673a0
Update dependencies from https://github.com/dotnet/toolset build 20190624.3 (#2608)
- Microsoft.Dotnet.Toolset.Internal - 3.0.100-preview7.19324.3
2019-06-24 13:24:41 +00:00
eng Update dependencies from https://github.com/dotnet/toolset build 20190624.3 (#2608) 2019-06-24 13:24:41 +00:00
resources/images Publishes the binaries and native installers. 2018-12-19 16:08:49 -08:00
src Consolidate MSBuild* versions for source-build (#2554) 2019-06-20 15:24:02 -07:00
test Re-enable .NET Core 2.2 tests 2019-06-18 16:26:57 -07:00
TestAssets [master] Update dependencies from dotnet/toolset (#1161) 2019-03-31 01:02:28 +00: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 Updating the YAML file to run ci and signing. 2018-12-20 15:25:20 -08:00
.vsts-ci.yml Update .vsts-ci.yml (#1978) 2019-05-14 09:47:31 -07:00
build.cmd Build script fixes for CI 2018-11-07 17:21:16 -08:00
build.sh Attempt to disable pretty print control codes for CI 2018-11-08 00:36:11 -08: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 Add a fake nupkg project to be published to make dependency uptake easier 2019-03-20 13:31:47 -07:00
Directory.Build.targets Add arcade infrastructure 2018-10-21 22:07:26 -07:00
global.json Update dependencies from https://github.com/dotnet/arcade build 20190623.4 (#2604) 2019-06-24 12:29:04 +00:00
LICENSE [master] Update dependencies from dotnet/arcade (#1056) 2019-03-20 21:42:05 +00:00
Microsoft.DotNet.Cli.sln make publish of internal asset conditional (#1832) 2019-05-02 10:50:02 -07:00
netci.groovy Fix bad merge to netci.groovy 2018-07-31 16:25:02 -07:00
NuGet.config remove unneeded line from nuget.config 2019-01-11 13:19:39 -06:00
PULL_REQUEST_TEMPLATE add PR template 2016-05-03 14:15:14 -07:00
README.md Add gRPC NuGet feed 2019-05-24 13:59:36 -07: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
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

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 V2 of the .NET Core tooling?

Download v2.0 of the .NET Core tools (CLI, MSBuild and the new csproj) at https://dot.net/core.

Note: The master branch of the .NET Core SDK repo is based on an forthcoming version of the SDK and is pre-release. For production-level usage, use the released version of the tools available 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.

To download the .NET Core runtime without the SDK, visit https://github.com/dotnet/core-setup#daily-builds.

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.

Example:

<configuration>
  <packageSources>
    <add key="dotnet-core" value="https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json" />
    <add key="dotnet-windowsdesktop" value="https://dotnetfeed.blob.core.windows.net/dotnet-windowsdesktop/index.json" />
    <add key="aspnet-aspnetcore" value="https://dotnetfeed.blob.core.windows.net/aspnet-aspnetcore/index.json" />
    <add key="aspnet-aspnetcore-tooling" value="https://dotnetfeed.blob.core.windows.net/aspnet-aspnetcore-tooling/index.json" />
    <add key="aspnet-entityframeworkcore" value="https://dotnetfeed.blob.core.windows.net/aspnet-entityframeworkcore/index.json" />
    <add key="aspnet-extensions" value="https://dotnetfeed.blob.core.windows.net/aspnet-extensions/index.json" />
    <add key="gRPC repository" value="https://grpc.jfrog.io/grpc/api/nuget/v3/grpc-nuget-dev" />
  </packageSources>
</configuration>
Platform Master
(3.0.x Runtime)
Release/3.0.1XX
(3.0.x Runtime)
Release/2.2.3XX
(2.2.x Runtime)
Release/2.2.2XX
(2.2.x Runtime)
Release/2.2.1XX
(2.2.x Runtime)
Release/2.1.7XX
(2.1.7 Runtime)
Release/2.1.6XX
(2.1.6 Runtime)
Release/2.1.5XX
(2.1.5 Runtime)
Windows x64
Installer - Checksum
zip - Checksum

Installer - Checksum
zip - Checksum

Installer - Checksum
zip - Checksum

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

Installer - Checksum
zip - Checksum

Installer - Checksum
zip - Checksum

Installer - Checksum
zip - Checksum
macOS
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

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

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

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

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum
RHEL 6
tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum
Linux-musl
tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum

tar.gz - Checksum
Windows arm
zip - Checksum

zip - Checksum

zip - Checksum

zip - Checksum

zip - Checksum
N/A N/A N/A
FreeBSD x64
tar.gz - Checksum

tar.gz - Checksum
N/A N/A N/A N/A N/A N/A
Constituent Repo Shas N/A Git SHAs N/A 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:

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.