5ebc6a1ceb
* Eliminate CleanPublishOutput * Decompose Crossgen Task * WiP * TarGzFileExtractToDirectory * FixModeFlags --> CHMod Also various eliminations of dead code * Tasks cleanup Move all tasks to .tasks file. There is little value in keepint them in each source file as they are already being used assumptively by files that happen to get executed later. Also eliminating uses of <Exec> for DotNet invocations * Move to BuildTools implementation of TarGzCreateFromDirectory * Eliminate Command.cs and helpers * Remove dead code * Revert TarGz from BuildTools Latest build tools package has not picked up the task, though it is checked in. * Disable ChMod on Windows * Windows bug fix * PR Feedback * Finish changing Chmod caps |
||
|---|---|---|
| build | ||
| build_projects | ||
| Documentation | ||
| packaging | ||
| resources/images | ||
| scripts | ||
| src | ||
| test | ||
| TestAssets | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| branchinfo.txt | ||
| build.cmd | ||
| build.proj | ||
| build.sh | ||
| BuildToolsVersion.txt | ||
| CONTRIBUTING.md | ||
| global.json | ||
| init-tools.ps1 | ||
| init-tools.sh | ||
| ISSUE_TEMPLATE | ||
| LICENSE | ||
| Microsoft.DotNet.Cli.sln | ||
| netci.groovy | ||
| NuGet.Config | ||
| NuGet.master.config | ||
| omnisharp.json | ||
| PULL_REQUEST_TEMPLATE | ||
| README.md | ||
| run-build.ps1 | ||
| run-build.sh | ||
| THIRD-PARTY-NOTICES | ||
.NET Command Line Interface
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 flavours:
- .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.