| build | ||
| build_projects | ||
| buildpipeline | ||
| Documentation | ||
| packaging | ||
| resources | ||
| scripts | ||
| src | ||
| test | ||
| TestAssets | ||
| tools | ||
| .cliversion | ||
| .gitattributes | ||
| .gitignore | ||
| .toolversions | ||
| branchinfo.txt | ||
| build.cmd | ||
| build.proj | ||
| build.sh | ||
| clean.cmd | ||
| clean.sh | ||
| config.json | ||
| CONTRIBUTING.md | ||
| dir.props | ||
| dir.tasks | ||
| global.json | ||
| 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 | ||
| run.cmd | ||
| run.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.
RC 4 release - MSBuild based tools
As was outlined in the "Changes to project.json" blog post, we have started work to move away from project.json to csproj and MSBuild. All the new latest releases from this repo (from rel/1.0.0 branch) are MSBuild-enabled tools.
The current official release of the csproj-enabled CLI tools is CLI RC 4.
There are a couple of things to keep in mind:
- RC 4 CLI bits are still in development so some rough edges are to be expected.
- RC 4 bits do not support project.json so you will have to either keep Preview 2 tools around or migrate your project or add a global.json file to your project to target preview2. You can find more information on this using the project.json to csproj instructions.
- RC 4 refers to the CLI tools only and does not cover Visual Studio, VS Code or Visual Studio for Mac.
- We welcome any and all issues that relate to MSBuild-based tools, so feel free to try them out and leave comments and file any bugs/problems.
Download links
- Instructions and links for download: RC3 download links.
- Directory for future Preview release notes: .NET Core release notes.
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 | Ubuntu 16.10 | Debian 8.2 | Windows x64 | Windows x86 | Mac OS X | CentOS 7.1 / Oracle Linux 7.1 | RHEL 7.2 | OpenSUSE 13.2 | OpenSUSE 42.1 | Fedora 23 | Fedora 24 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Installers and Binaries
You can download .NET Core SDK as either an installer (MSI, PKG) or a zip (zip, tar.gz). .NET Core SDK contains both the .NET Core runtime and CLI tools.
In order to download just the .NET Core runtime without the SDK, please visit https://github.com/dotnet/core-setup#daily-builds.
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.)
| Platform | rel/1.1.0 |
|---|---|
| Windows x64 | Installer - Checksum zip - Checksum |
| Windows x86 | Installer - Checksum zip - Checksum |
| Ubuntu 14.04 / Linux Mint 17 | Installer - Checksum *See Installer Note Below tar.gz - Checksum |
| Ubuntu 16.04 | Installer - Checksum *See Installer Note Below tar.gz - Checksum |
| Ubuntu 16.10 | Installer - Checksum *See Installer Note Below tar.gz - Checksum |
| Debian 8.2 | tar.gz - Checksum |
| Mac OS X | Installer - Checksum tar.gz - Checksum |
| CentOS 7.1 / Oracle Linux 7 | tar.gz - Checksum |
| RHEL 7.2 | tar.gz - Checksum |
| openSUSE 13.2 | tar.gz - Checksum |
| openSUSE 42.1 | tar.gz - Checksum |
| Fedora 23 | tar.gz - Checksum |
| Fedora 24 | tar.gz - Checksum |
Note: 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 the corresponding Host, Host FX Resolver, and Shared Framework packages before installing the Sdk package.
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.