5cdf1e7ab6
Allows the argument passed to dotnet compile --native --ilcpath to be either end with ilc.exe, or with the directory that contains ilc.exe. Fix #768 |
||
|---|---|---|
| Documentation | ||
| packaging | ||
| scripts | ||
| src | ||
| test | ||
| testapp | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| bin | ||
| build.cmd | ||
| build.sh | ||
| CONTRIBUTING.md | ||
| global.json | ||
| LICENSE | ||
| Microsoft.DotNet.Cli.sln | ||
| netci.groovy | ||
| NuGet.Config | ||
| NuGet.master.config | ||
| omnisharp.json | ||
| README.md | ||
| 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.
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 | |
|---|---|---|---|---|
| Debug | ||||
| Release |
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
This 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.
Questions & Comments
For any and all feedback, please use the Issues on this repository.