This repo contains the .NET Core command-line (CLI) tools, used for building .NET Core apps and libraries through your development flow (compiling, NuGet package management, running, testing, ...).
C# Shell PowerShell Dockerfile Groovy Batchfile Other
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
Documentation Merge branch 'master' into merges/release/2.2.1xx-to-master Aug 6, 2018
TestAssets Merge branch 'master' into merges/release/2.2.1xx-to-master Aug 9, 2018
build Merge pull request #9805 from dotnet/merges/release/2.2.1xx-to-master Aug 21, 2018
build_projects Remove files due to bad merge Aug 20, 2018
packaging/windows Fix Windows build Aug 5, 2018
resources Remove ImportAfter target for NuGet Oct 25, 2017
scripts Change script to be in sync with dotnet.exe location Aug 20, 2018
src Merge pull request #9805 from dotnet/merges/release/2.2.1xx-to-master Aug 21, 2018
test Merge pull request #9805 from dotnet/merges/release/2.2.1xx-to-master Aug 21, 2018
tools Merge branch 'dev/release/2.0' into merge_dev_release_20 Dec 8, 2017
.editorconfig Checkin corefx editorconfig Sep 18, 2017
.gitattributes Treat xlf as text Dec 8, 2017
.gitignore Create binlogs by default. Jul 27, 2018 merge master Mar 20, 2017
Directory.Build.props Retarget to netcoreapp3.0 / netstandard2.0 Aug 3, 2018
ISSUE_TEMPLATE issue template, the --info is the new --version Mar 31, 2016
LICENSE Initial commit Oct 2, 2015
Microsoft.DotNet.Cli.sln Remove the test project in sln Aug 20, 2018
PULL_REQUEST_TEMPLATE add PR template May 3, 2016 Merge branch 'master' into merges/release/2.2.1xx-to-master Jul 20, 2018
THIRD-PARTY-NOTICES Add license text to LZMA SDK license notice Feb 26, 2017
build.cmd The modification to build.cmd did not have the desired effect. Nov 29, 2017
build.proj Merge branch 'master' into merge_master_into_repo_refactoring May 22, 2018 Add Dockerfile for RHEL 6 builds Sep 26, 2017
dir.props Adding consistent "Project" headers to inported props and target files. Sep 27, 2017
dir.tasks Bump MSBuild Version to 15.1.0-preview-000503-01 (#5199) Jan 5, 2017
netci.groovy Fix the CI legs; CLI:release/2.1.3xx (#9535) Jun 22, 2018
run-build.ps1 Merge branch 'master' into merges/release/2.2.1xx-to-master Aug 6, 2018 Merge branch 'master' into merges/release/2.2.1xx-to-master Aug 6, 2018
testAsset.props Retarget to netcoreapp3.0 / netstandard2.0 Aug 3, 2018

.NET Command Line Interface

Join the chat at

This repo contains the source code for cross-platform .NET Core command line toolchain. It contains the implementation of each command and the documentation.

Looking for the .NET Core SDK tooling?

If you are looking for the latest nightly of the .NET Core SDK, see

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

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.


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