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
2017-06-23 11:51:11 -07:00
build MSBuild 15.3.400 2017-06-21 18:18:30 -05:00
build_projects Merge pull request #6857 from johnbeisner/RuntimeCoherence 2017-06-15 10:22:40 -07:00
Documentation Updates to DEB packaging and publishing. 2017-06-06 15:26:04 -07:00
packaging Add dummy eula for Windows installer 2017-06-22 09:03:35 -07:00
resources Return non-zero exit code for test failure in multitargeted test project. 2016-12-16 15:39:52 +05:30
scripts Merge pull request #6857 from johnbeisner/RuntimeCoherence 2017-06-15 10:22:40 -07:00
src Add msbuild satellite assemblies 2017-06-21 13:34:16 -07:00
test Merge pull request #6974 from nguerrera/msbuild-satellites 2017-06-21 18:03:25 -07:00
TestAssets Updating the SDK. Mostly, had to change PackageTargetFallback to AssetTargetFallback. 2017-06-14 00:27:26 -07:00
tools Merge branch 'rel/1.1.0' into merge_rel_110 2017-06-01 09:43:31 -07:00
.gitattributes Add props and targets to text=auto 2017-06-07 16:37:43 -07:00
.gitignore Add .binlog (MSBuild binary log format) extension to .gitignore 2017-04-27 09:29:15 -07:00
build.cmd Bypass powershell execution policy 2017-03-15 14:01:27 -07:00
build.proj Turning off implicit restore when publishing the build project. 2017-06-08 17:00:01 -07:00
build.sh Adding a comment about the code that removes empty spaces from the arguments array but also breaks quoted arguments. We are picking the devil we know in this case. 2016-07-12 11:23:34 -07:00
CONTRIBUTING.md Fix broken links from #5928 in the documentation. 2017-03-12 19:46:28 +01:00
dir.props Stop produce duplicated package for VSTS build definition 2017-06-16 07:32:20 -07:00
dir.tasks Bump MSBuild Version to 15.1.0-preview-000503-01 (#5199) 2017-01-05 14:56:11 -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 Stop produce duplicated package for VSTS build definition 2017-06-16 07:32:20 -07:00
netci.groovy Add CROSS check 2017-05-15 11:47:42 -07:00
NuGet.Config Merge remote-tracking branch 'dotnet/rel/1.1.0' into merges/rel/1.1.0-to-release/2.0.0-20170621-070038 2017-06-21 08:49:31 -07:00
NuGet.master.config add readme 2015-10-08 14:41:04 -07:00
PULL_REQUEST_TEMPLATE add PR template 2016-05-03 14:15:14 -07:00
README.md Update README.md 2017-06-23 11:51:11 -07:00
run-build.ps1 Updates to install scripts to consume the renaming packages at blob storage. Unpinning the CLI build from a specific version. 2017-06-07 10:18:05 -07:00
run-build.sh Stop produce duplicated package for VSTS build definition 2017-06-16 07:32:20 -07:00
testAsset.props Replacing hard coded references to shared framework version. 2017-03-06 21:25:42 -08: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 v1.0.1 release of the .NET Core tools (CLI, MSBuild and the new csproj), see https://dot.net/core.

Note: the release/2.0.0 branch of the CLI repo is based on the upcoming v2 of .NET Core and is considered pre-release. For production-level usage, use v1 of the tools.

Found an issue?

You can consult the known issues page to find out the current issues and to see 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

Ubuntu 14.04 / Linux Mint 17 Ubuntu 16.04 Ubuntu 16.10 Debian 8 Windows x64 Windows x86 macOS CentOS 7.1 / Oracle Linux 7.1 RHEL 7.2 Linux x64

Installers and Binaries

You can download .NET Core SDK as either an installer (MSI, PKG) or a zip (zip, tar.gz). .NET Core SDK contains both the .NET Core runtime and CLI tools.

In order to download the .NET Core runtime without the SDK, see https://github.com/dotnet/core-setup#daily-builds.

Note: The following installers are the latest prerelease bits. If you want to install the latest released versions, see the preceding section.

Platform release/2.0.0
Windows x64 Installer - Checksum
zip - Checksum
Windows x86 Installer - Checksum
zip - Checksum
Mac OS X Installer - Checksum
tar.gz - Checksum
Linux x64 tar.gz - Checksum
Ubuntu 14.04 / Linux Mint 17 Installer - Checksum
*See Installer Note Below
tar.gz - See Linux x64
Ubuntu 16.04 Installer - Checksum
*See Installer Note Below
tar.gz - See Linux x64
Ubuntu 16.10 Installer - Checksum
*See Installer Note Below
tar.gz - See Linux x64
Debian 8 Installer - Checksum
*See Installer Note Below
tar.gz - See Linux x64
CentOS 7.1 / Oracle Linux 7 tar.gz - See Linux x64
RHEL 7.2 Installer - Checksum
*See Installer Note Below
tar.gz - See Linux x64
Fedora 24 tar.gz - See Linux x64
OpenSUSE 42.1 tar.gz - See Linux x64

Note: 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.

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

Ubuntu 16.10

sudo sh -c 'echo "deb [arch=amd64] http://apt-mo.trafficmanager.net/repos/dotnet/ yakkety 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, please 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 any and all feedback, please use the Issues on this repository.

License

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