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
Livar 2cc5612fec Merge pull request #6287 from dotnet/dev-ragrawal-updatenuget2484
update nuget version to 4.3.0-preview1-2500
2017-04-27 12:59:19 -07:00
build Merge pull request #6287 from dotnet/dev-ragrawal-updatenuget2484 2017-04-27 12:59:19 -07:00
build_projects Merge pull request #6362 from mlorbetske/dev/mlorbe/Update20Templates 2017-04-22 12:00:08 -07:00
Documentation tab completion documentation 2017-04-26 12:07:15 -07:00
packaging Prime cache for Windows 2017-04-26 14:44:23 -07:00
resources Return non-zero exit code for test failure in multitargeted test project. 2016-12-16 15:39:52 +05:30
scripts change script to assume dotnet is on the path 2017-04-26 11:25:29 -07:00
src fix NullReferenceError on remove package and incorrect help text 2017-04-26 16:43:55 -07:00
test fix NullReferenceError on remove package and incorrect help text 2017-04-26 16:43:55 -07:00
TestAssets Adding a work around for a test failure. 2017-04-26 10:30:04 -07:00
tools Fix crossgen step on win10 box 2017-03-21 19:28:09 -07:00
.cliversion Change stage0PJ version to preview2.1, which supports the new platforms. 2017-02-22 15:13:02 -06:00
.gitattributes merge my spike on compile/publish/run and switch from PS1 to C# 2015-10-06 10:46:43 -07:00
.gitignore add *.xproj.user to backup file types 2016-11-16 01:10:55 -08:00
.toolversions Update buildtools to 1.0.27-prerelease-01316-08 2017-02-22 15:13:02 -06:00
build.cmd Bypass powershell execution policy 2017-03-15 14:01:27 -07:00
build.proj Fixing the extra distros. 2017-03-20 12:41:47 -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
clean.cmd Bringing run.exe into the repo and starting with the clean command 2016-07-26 16:15:36 -07:00
clean.sh Bringing run.exe into the repo and starting with the clean command 2016-07-26 16:15:36 -07:00
config.json Bringing run.exe into the repo and starting with the clean command 2016-07-26 16:15:36 -07:00
CONTRIBUTING.md Fix broken links from #5928 in the documentation. 2017-03-12 19:46:28 +01:00
dir.props Updating the stage0 in release/2.0.0 to use a release/2.0.0 stage0 and turning off implicit package target fallback in the CLI. 2017-04-27 09:29:39 -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 fix NullReferenceError on remove package and incorrect help text 2017-04-26 16:43:55 -07:00
netci.groovy Add help job 2017-03-30 19:40:03 +09:00
NuGet.Config Update to latest ASP.NET package versions & fix feed entry in NuGet.config 2017-04-25 21:31:12 -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 Reverting some files that we don't want integrated back to master. 2017-04-26 11:45:26 -07:00
run-build.ps1 Reverting channel changes for stage0. In master we want to continue using the master channel. 2017-04-27 11:07:50 -07:00
run-build.sh Reverting channel changes for stage0. In master we want to continue using the master channel. 2017-04-27 11:07:50 -07:00
run.cmd Bringing run.exe into the repo and starting with the clean command 2016-07-26 16:15:36 -07:00
run.sh Bringing run.exe into the repo and starting with the clean command 2016-07-26 16:15:36 -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 as well as 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), head over to https://dot.net/core and download!

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

Found an issue?

You can consult the known issues page 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

Ubuntu 14.04 / Linux Mint 17 Ubuntu 16.04 Debian 8.2 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 just the .NET Core runtime without the SDK, please visit https://github.com/dotnet/core-setup#daily-builds.

Note: please be aware that below installers are the latest bits. If you want to install the latest released versions, please check out the section above.

Platform master
Windows x64 Installer - Checksum
zip - Checksum
Windows x86 Installer - Checksum
zip - Checksum
Ubuntu 14.04 / Linux Mint 17 Installer - Checksum
*See Installer Note Below
tar.gz - Checksum
Ubuntu 16.04 tar.gz - Checksum
Debian 8.2 tar.gz - Checksum
macOS Installer - Checksum
tar.gz - Checksum
CentOS 7.1 / Oracle Linux 7 tar.gz - Checksum
RHEL 7.2 tar.gz - Checksum
Linux x64 tar.gz - Checksum

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:

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

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.