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-02-11 22:29:20 -08:00
Documentation Argument Fowarding Tests should account for newline added by StreamFowarder. Add an entry to developer guide so command developers will use Console.WriteLine. PR feedback and slight refactoring. 2016-02-08 14:19:03 -08:00
packaging Upload bundles instead of MSI 2016-02-10 13:06:48 -08:00
resources/images Responding to PR feedback, adding the OS names 2016-02-03 09:46:45 -08:00
scripts Refactoring dotnet-compile to make adding the script variable testable. So far, moved it to have a compiler controller and two separate compilers: native and managed. Also moved the script runner to its own class so that we can mock it into the managed controller. 2016-02-11 12:42:02 -08:00
src Use ApplicationBasePath instead of entry assembly to locate reference 2016-02-11 22:29:20 -08:00
test Replacing the fixed rid in the dotnet compile unit test by one that respects the platform where the tests are running. 2016-02-11 12:44:27 -08:00
testapp update everyone to 23811 2016-02-11 10:38:59 -08:00
TestAssets update everyone to 23811 2016-02-11 10:38:59 -08:00
tools update everyone to 23811 2016-02-11 10:38:59 -08:00
.gitattributes merge my spike on compile/publish/run and switch from PS1 to C# 2015-10-06 10:46:43 -07:00
.gitignore Responding to PR feedback. 2016-02-03 09:46:45 -08:00
build.cmd Maintain test artifacts 2016-01-26 23:25:39 -08:00
build.sh Fix the correct path to package.sh when packaging inside docker. 2016-01-07 19:24:34 -08:00
CONTRIBUTING.md Add contributing info and developer guide 2015-11-17 23:26:58 -08:00
global.json remove extra comma 2016-02-05 17:23:12 +01:00
LICENSE Initial commit 2015-10-02 11:03:16 -07:00
Microsoft.DotNet.Cli.sln Refactoring dotnet-compile to make adding the script variable testable. So far, moved it to have a compiler controller and two separate compilers: native and managed. Also moved the script runner to its own class so that we can mock it into the managed controller. 2016-02-11 12:42:02 -08:00
netci.groovy Move to auto-images 2016-02-08 16:17:00 -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 Add omnisharp.json file to exclude test projects from editor 2015-10-29 01:48:46 -07:00
README.md Upload bundles instead of MSI 2016-02-10 13:06:48 -08: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/

Build Status

Ubuntu 14.04 Windows Mac OS X CentOS 7.1

Installers

Ubuntu 14.04 Windows Mac OS X CentOS 7.1
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 5 RC bits?

This toolchain is independent from the DNX-based .NET Core + ASP.NET 5 RC bits. If you are looking for .NET Core + ASP.NET 5 RC 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]/[binary name] that you can just run.

Finally, you can also try out native compilation using RyuJIT as shown below:

dotnet build --native

The following command will perform native compilation using the C++ Codegenerator:

dotnet build --native --cpp

If you are in Windows, make sure that you run the above command inside the VS 2015 x64 Native Tools prompt, otherwise you will get errors. This command will drop a native single binary in ./bin/[configuration]/[framework]/native/[binary name] that you can run.

Note: At this point, only the helloworld and dotnetbot samples will work with native compilation.

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.

Also, when building from source, you need to set up the DOTNET_HOME environment variable. It needs to point to the parent directory of where bin and runtime directories are.

Known issues

You can also consult the known issues page to find out the current issues and to see the workarounds.

Questions & Comments

For any and all feedback, please use the Issues on this repository.