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-10-28 13:40:19 -07:00
build Merge from rel/1.0.0 2016-10-28 17:56:24 +05:30
build_projects [WIP] Removes *3 verbs, making msbuild the driver (#4456) 2016-10-27 18:46:43 -07:00
Documentation Merge pull request #4006 from svick/patch-4 2016-10-25 17:04:29 -07:00
packaging Create a nuget package with the windows installers. 2016-10-05 13:56:57 -07:00
resources 1) Added support to run test from test3 verb for the project targeting multiple TFM 2016-10-25 20:10:18 +05:30
scripts Merge pull request #4448 from jgalar/patch-1 2016-10-21 19:49:36 -07:00
src 1) Added diag support 2016-10-28 20:15:38 +05:30
test 1) Added diag support 2016-10-28 20:15:38 +05:30
TestAssets Remove Unicdoe Path 2016-10-28 13:40:19 -07:00
tools Add support for Migration defaults (#4242) 2016-10-20 11:00:41 -07:00
.cliversion [WIP] Removes *3 verbs, making msbuild the driver (#4456) 2016-10-27 18:46:43 -07:00
.gitattributes merge my spike on compile/publish/run and switch from PS1 to C# 2015-10-06 10:46:43 -07:00
.gitignore [WIP] Removes *3 verbs, making msbuild the driver (#4456) 2016-10-27 18:46:43 -07:00
.toolversions Switch to using new bootstrap script to initialize buildtools. (#4349) 2016-10-25 16:51:41 -07:00
branchinfo.txt Fixing the version back to preview3 and the channel to rel-1.0.0 2016-08-30 21:32:45 -07:00
build.cmd Merge rel/1.0.0 into feature/msbuild. 2016-07-18 14:44:06 -05:00
build.proj Change cli build to csproj files (First step on one project) 2016-10-13 18:09:30 -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 Add contributing info and developer guide 2015-11-17 23:26:58 -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 Add test for dotnet run with multiple frameworks. 2016-10-17 21:03:08 -05:00
netci.groovy update netci.groovy to use ubuntu.14.04 2016-06-01 16:47:46 -07:00
NuGet.Config Updating the xunit version to match the new version of dotnet-test-xunit. 2016-08-10 13:40:27 -07:00
NuGet.master.config add readme 2015-10-08 14:41:04 -07:00
omnisharp.json Update omnisharp setting. Disable auto restore. 2016-03-27 12:12:57 -07:00
PULL_REQUEST_TEMPLATE add PR template 2016-05-03 14:15:14 -07:00
README.md [Build kick-off] Change underline to match length 2016-10-27 16:02:05 -07:00
run-build.ps1 Fix build scripts to pass architecture into the bootstrapper. 2016-10-27 11:56:57 -05:00
run-build.sh Fix build scripts to pass architecture into the bootstrapper. 2016-10-27 11:56:57 -05: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
THIRD-PARTY-NOTICES Add LZMA to THIRD-PARTY-NOTICES + (c) header 2016-06-14 10:29:23 -07: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.

RTM and Preview 2 bits

To get the latest released bits (RTM for .NET Core and Preview 2 for tooling), check out our Getting started page.

Also, don't forget to check out the documentation.

Changes in issue triaging

We are making significant changes to the CLI tooling by supporting MSBuild as the build engine and csproj as the project format. You can read "Changes to project.json" blog post for more context. We've realized that this also means that many of the shortcomings of the current tooling will be solved by this move so we've decided to introduce two new labels to indicate that in the issues:

  • msbuild-mitigated - this label indicates the issue will be mitigated via move to MSBuild.
  • msbuild-notapplicable - this label indicates the issue will not be applicable after moving to MSBuild.

We will close issues that are labelled with one of these labels. Proactive triaging will help us reduce the number of issues and enable us to focus on issues that require fixing independent of the move to msbuild.

Please feel free to re-open and comment on any issue that you believe was triaged incorrectly.

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 Mac OS X CentOS 7.1 / Oracle Linux 7.1 RHEL 7.2 OpenSUSE 13.2 Fedora 23

Installers and Binaries

You can download .NET Core as either an installer (MSI, PKG) or a zip (zip, gzip). You can download the product in two flavors:

  • .NET Core - .NET Core runtime and framework
  • .NET Core SDK - .NET Core + CLI tools

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.)

Version .NET Core Installer .NET Core SDK Installer .NET Core Binaries .NET Core SDK Binaries
Windows x64 Download Download Download Download
Windows x86 Download Download Download Download
Ubuntu 14.04 / Linux Mint 17 See Below See Below Download Download
Ubuntu 16.04 N/A N/A Download Download
Debian 8.2 N/A N/A Download Download
Mac OS X Download Download Download Download
CentOS 7.1 / Oracle Linux 7 N/A N/A Download Download
RHEL 7.2 N/A N/A Download Download
openSUSE 13.2 N/A N/A Download Download
Fedora 23 N/A N/A Download Download

Ubuntu Installers

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 them in the order presented below.

**For Ubuntu 14.04

Version Installers
Shared Host Download
Host Framework Resolver Download
Shared Framework Download
Sdk Download

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.