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
2016-03-04 11:01:15 -08:00
Documentation Update and rename installation-scenarios.md to cli-installation-scenarios.md 2016-03-02 17:27:46 -08:00
packaging Merge pull request #1551 from Sridhar-MS/cli-x86-support 2016-02-29 14:59:51 -08:00
resources/images Update version_badge.svg 2016-02-17 23:54:07 -08:00
scripts Move to CoreFX build rc2-23901 2016-03-03 16:41:55 -06:00
src Finish builder tests 2016-03-04 11:01:15 -08:00
test Finish builder tests 2016-03-04 11:01:15 -08:00
TestAssets Move to CoreFX build rc2-23901 2016-03-03 16:41:55 -06:00
tools Move to CoreFX build rc2-23901 2016-03-03 16:41:55 -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 working on build scripts 2016-02-12 15:26:35 -08:00
branchinfo.txt working on build scripts 2016-02-12 15:26:35 -08:00
build.cmd working on build scripts 2016-02-12 15:26:35 -08:00
build.sh Fix release builds in docker. 2016-02-17 16:16:25 -08:00
CONTRIBUTING.md Add contributing info and developer guide 2015-11-17 23:26:58 -08:00
global.json Update global.json 2016-02-25 00:04:17 -08:00
ISSUE_TEMPLATE Responding to PR feedback 2016-02-26 21:11:32 -08:00
LICENSE Initial commit 2015-10-02 11:03:16 -07:00
Microsoft.DotNet.Cli.sln General cleanup of the solution. Removed non-existant projects, fixed paths, removed invalid projects, etc. 2016-02-24 09:02:42 -08:00
netci.groovy Add '--targets' option to the build scripts which take a comma separated 2016-02-29 13:05:38 -08:00
NuGet.Config Updating NuGet.config to no longer point to myget.org. 2016-02-03 15:25:48 -06:00
NuGet.master.config add readme 2015-10-08 14:41:04 -07:00
omnisharp.json Fixing versions 2016-02-18 01:10:07 -08:00
README.md Links to dev docs in root readme 2016-02-25 09:58:24 +00:00
THIRD-PARTY-NOTICES Add 3rd party notices 2015-11-17 08:21:09 -08:00

.NET Command Line Interface

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.

New to .NET CLI?

Check out our http://dotnet.github.io/getting-started/ page.

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.

Build Status

Ubuntu 14.04 Windows Mac OS X CentOS 7.1

Installers

Ubuntu 14.04 Windows Mac OS X CentOS 7.1
Version
Installers Download Debian Package Download Msi Download Pkg N/A
Binaries Download tar file Download zip file Download tar file Download tar file

Interested in .NET Core + ASP.NET Core 1.0 RC1 bits?

This toolchain is independent from the DNX-based .NET Core + ASP.NET Core 1.0 RC1 bits. If you are looking for .NET Core + ASP.NET Core 1.0 RC1 bits, you can find instructions on the http://get.asp.net/.

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 a binary in ./bin/[configuration]/[framework]/[rid]/[binary name] that you can just run.

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.