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
2018-06-03 08:45:34 -07:00
build Remove -upgrade suffix from installer inputs 2018-06-03 08:45:34 -07:00
build_projects Replace alpine with linux-musl builds 2018-04-20 13:23:00 -07:00
Documentation Update dotnet manpages for Unix 2018-04-17 06:08:15 +00:00
packaging Updating the CLI branding to 201. 2018-05-11 12:33:12 -07:00
resources Remove ImportAfter target for NuGet 2017-10-25 16:41:57 -07:00
scripts Merge remote-tracking branch 'dotnet/release/2.1.2xx' into merges/release/2.1.2xx-to-release/2.1.3xx 2018-05-03 15:24:39 -07:00
src Add retry when Directory.Move (#9313) 2018-06-01 11:22:03 -07:00
test Fix mismatch of dotnet-watch with package variable name 2018-05-31 14:44:29 -07:00
TestAssets Fix Razor server shutdown on Windows. 2018-04-27 13:52:17 -07:00
tools Merge remote-tracking branch 'dotnet/release/15.5' into merges/release/15.5-to-master-20171206-080040 2017-12-07 09:55:12 -08: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 Merge branch 'master' into merges/release/15.5-to-master-20171204-080035 2017-12-04 11:20:08 -08:00
build.cmd The modification to build.cmd did not have the desired effect. 2017-11-28 19:00:51 -08:00
build.proj Merge remote-tracking branch 'dotnet/release/15.5' into merges/release/15.5-to-master-20171206-080040 2017-12-07 09:55:12 -08:00
build.sh Add Dockerfile for RHEL 6 builds 2017-09-26 11:50:50 -07:00
CONTRIBUTING.md Fix broken links from #5928 in the documentation. 2017-03-12 19:46:28 +01:00
dir.props Changes in the Transport feed DLL requires our response; update Transport feed DLL version and base URL. 2017-11-08 19:07:29 -08:00
dir.tasks Bump MSBuild Version to 15.1.0-preview-000503-01 (#5199) 2017-01-05 14:56:11 -08:00
Directory.Build.props bundled DotnetTool (#8606) 2018-02-16 13:32:29 -08:00
global.json Fix the update-dependencies project so it builds and runs again. 2016-05-16 19:10:04 -05:00
ISSUE_TEMPLATE issue template, the --info is the new --version 2016-03-31 12:34:28 +02:00
LICENSE Initial commit 2015-10-02 11:03:16 -07:00
Microsoft.DotNet.Cli.sln Apphost shim (#8893) 2018-04-02 12:37:25 -07:00
netci.groovy Merge pull request #9318 from dotnet/merges/release/2.1.2xx-to-release/2.1.3xx 2018-05-21 09:24:15 -07:00
PULL_REQUEST_TEMPLATE add PR template 2016-05-03 14:15:14 -07:00
README.md Update readme: alpine-<ver>-targz to musl-targz 2018-04-26 16:58:49 +00:00
run-build.ps1 Merge remote-tracking branch 'dotnet/release/2.1.2xx' into merges/release/2.1.2xx-to-release/2.1.3xx 2018-05-03 15:24:39 -07:00
run-build.sh Removing some patches for source build. 2018-05-02 11:59:01 -07:00
testAsset.props Modifying testAsset.props so that when loading DependencyVersions.props, we also load OrchestratedPackageVersions.props if it exists. This fixes cases where a single project ended up being restored and built with different versions of Microsoft.NetCore.App in ProdCon. 2018-03-31 21:07:31 -07:00
THIRD-PARTY-NOTICES Add license text to LZMA SDK license notice 2017-02-26 12:11:05 -08:00

.NET Command Line Interface

.NET Slack Status Join the chat at https://gitter.im/dotnet/cli

This repo contains the source code for cross-platform .NET Core command line toolchain. It contains the implementation of each command, the native packages for various supported platforms and the documentation.

Looking for V1 of the .NET Core tooling?

If you are looking for the v2.0 release of the .NET Core tools (CLI, MSBuild and the new csproj), head over to https://dot.net/core and download!

Note: the release/2.1.3xx branch of the CLI repo is based on an upcoming update of the SDK and is considered pre-release. For production-level usage, please use the released version of the tools available at https://dot.net/core

Found an issue?

You can consult the Documents Index to find out the current issues and to see the workarounds.

If you don't find your issue, please file one! However, given that this is a very high-frequency repo, we've setup some basic guidelines to help you. Please consult those first.

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

Windows x64 Windows x86 macOS Linux x64 Archive Linux arm Archive Linux arm64 Archive Linux Native Installers RHEL 6 Archive Linux-musl Archive

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. In order to be able to restore these pre-release packages, you may need to add a NuGet feed pointing to https://dotnet.myget.org/F/dotnet-core/api/v3/index.json. Other feeds may also be necessary depending on what kind of project you are working with.

Platform Latest Daily Build
release/2.1.3xx
Windows x64 Installer - Checksum
zip - Checksum
Windows x86 Installer - Checksum
zip - Checksum
macOS Installer - Checksum
tar.gz - Checksum
Linux x64 DEB Installer - Checksum
RPM Installer - Checksum
see installer note below1
tar.gz - Checksum
Linux arm tar.gz - Checksum
Linux arm64 tar.gz - Checksum
RHEL 6 tar.gz - Checksum
Linux-musl tar.gz - Checksum
Latest Coherent Build2
release/2.1.3xx

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 these directly from the .deb files (via dpkg or similar), then you'll need to install the corresponding Host, Host FX Resolver, and Shared Framework packages before installing the Sdk package.

2: A 'coherent' build is defined as a build where the Runtime version matches between the CLI and Asp.NET.

Debian daily feed

Newest SDK binaries for 2.0.0 in debian feed may be delayed due to external issues by up to 24h.

Obtaining binaries

Add debian feed:

Ubuntu 14.04

sudo sh -c 'echo "deb [arch=amd64] http://apt-mo.trafficmanager.net/repos/dotnet/ trusty main" > /etc/apt/sources.list.d/dotnetdev.list'

sudo apt-key adv --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893

sudo apt-get update

Ubuntu 16.04

sudo sh -c 'echo "deb [arch=amd64] http://apt-mo.trafficmanager.net/repos/dotnet/ xenial main" > /etc/apt/sources.list.d/dotnetdev.list'

sudo apt-key adv --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893

sudo apt-get update

Debian 8

sudo sh -c 'echo "deb [arch=amd64] http://apt-mo.trafficmanager.net/repos/dotnet/ jessie main" > /etc/apt/sources.list.d/dotnetdev.list'

sudo apt-key adv --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893

sudo apt-get update

Install:

sudo apt-get install <DebianPackageName>=<Version>

To list available packages:

apt-cache search dotnet-sdk | grep 2.0.0

Docker

You can also use our Docker base images found on https://hub.docker.com/r/microsoft/dotnet to set up your dev or testing environment for usage.

Basic usage

When you have the .NET Command Line Interface installed on your OS of choice, you can try it out using some of the samples on the dotnet/core repo. You can download the sample in a directory, and then you can kick the tires of the CLI.

First, you will need to restore the packages:

dotnet restore

This will restore all of the packages that are specified in the project.json file of the given sample.

Then you can either run from source or compile the sample. Running from source is straightforward:

dotnet run

Compiling to IL is done using:

dotnet build

This will drop an IL assembly in ./bin/[configuration]/[framework]/[binary name] that you can run using dotnet bin/[configuration]/[framework]/[binaryname.dll].

For more details, refer to the documentation.

Building from source

If you are building from source, take note that the build depends on NuGet packages hosted on MyGet, so if it is down, the build may fail. If that happens, you can always see the MyGet status page for more info.

Read over the contributing guidelines and developer documentation for prerequisites for building from source.

Questions & Comments

For all feedback, use the Issues on this repository.

License

By downloading the .zip you are agreeing to the terms in the project EULA.