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
Sridhar Periyasamy 1db27b7ae3 Enable building dotnet-CLI for centos.
I had to patch up a redhat dnx package which supports NETStandard.Library package. It is currently uploaded to dotnet-cli blob storage. This hack will no longer be required when we move to xplat nuget to do 'dotnet restore'. Apart from this there are three issues that are tracked for centos.
- compile-native not yet supported - https://github.com/dotnet/cli/issues/453
- dnu restore crashes intermittently on centos. I need to investigate this a little bit more and file issues on dnx or coreclr. This will make our CI builds very flaky.
- Dotnet restore does not restore native shims when using “centos.7-x64” - https://github.com/dotnet/corefx/issues/5066
2015-12-18 11:32:20 -08:00
Documentation add spec for corehost 2015-12-16 15:48:18 -08:00
packaging Responding to PR feedback 2015-12-15 20:35:21 -08:00
scripts Enable building dotnet-CLI for centos. 2015-12-18 11:32:20 -08:00
src Enable building dotnet-CLI for centos. 2015-12-18 11:32:20 -08:00
test Enable native compilation JIT tests for Mac. 2015-12-17 14:53:57 -08:00
tools/MultiProjectValidator PR Feedback: match coding guidelines 2015-12-16 14:12:25 -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 remove c++ projects from sln 2015-12-01 11:42:02 -08:00
build.cmd workaround powershell bug 2015-11-24 19:41:00 -08:00
build.sh unify versions on binaries and nupkgs 2015-12-09 14:56:39 -08:00
CONTRIBUTING.md Add contributing info and developer guide 2015-11-17 23:26:58 -08:00
global.json PR Feedback 2015-12-08 10:54:03 -08:00
LICENSE Initial commit 2015-10-02 11:03:16 -07:00
Microsoft.DotNet.Cli.sln Multi Project Validator 2015-12-11 14:24:05 -08:00
netci.groovy Enable building dotnet-CLI for centos. 2015-12-18 11:32:20 -08:00
NuGet.Config Merge pull request #323 from Sridhar-MS/msi-unittests 2015-11-26 11:26:17 -08: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 Update README.md 2015-12-08 18:20:19 -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
Debug Build Status Build Status Build Status
Release Build Status Build Status Build Status

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 do you can kick the tires of the CLI.

Note: on Linux, post-install, please set up the DOTNET_HOME environment: export DOTNET_HOME=/usr/share/dotnet/.

Note: on OS X, post-install, please set up the DOTNET_HOME environment: export DOTNET_HOME=/usr/local/share/dotnet/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 compile

This will drop a binary in ./bin/[configuration]/[framework]/[binary name] that you can just run.

Finally, you can also try out native compilation on Windows and Ubuntu and Mac.

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

dotnet compile --native

On Mac OSX, we currently support the C++ Codegenerator (as shown below) and support for RyuJIT (as exemplified above) is coming soon.

dotnet compile --native --cpp

This will drop a native single binary in ./bin/[configuration]/[framework]/native/[binary name] that you can 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.

Questions & Comments

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