b6fcbbdd86
Support project.json compilationOptions: - nowarn - warningsAsErrors - keyFile - delaySign Use env var to configure compile-fsc behaviour: - DOTNET_FSC_PATH the fsc path. Default the bundled fsc.exe - DOTNET_COMPILEFSC_USE_RESPONSE_FILE if '1' then pass a response file to fsc instead of all arguments. Default pass all arguments - DOTNET_FSC_EXEC configure how to run the fsc. Values: - RUN run fsc passing fsc args - COREHOST run corehost passing fsc and fsc args. The default Use the same order of fsproj msbuild task for fsc arguments to make it easier compare fsproj build and .net cli build Fix --resource with path and name Enable --debug (-g) if pdb The generated assembly info file must be in the last - 1 position in source files list. 1. the generated assembly info file must be in the last possibile position to override the attributes 2. The last file is the source file with main |
||
|---|---|---|
| Documentation | ||
| packaging | ||
| resources/images | ||
| scripts | ||
| src | ||
| test | ||
| TestAssets | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| branchinfo.txt | ||
| build.cmd | ||
| build.sh | ||
| CONTRIBUTING.md | ||
| global.json | ||
| ISSUE_TEMPLATE | ||
| 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/ page.
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.
Build Status
| Ubuntu 14.04 | Windows x64 | Windows x86 | Mac OS X | CentOS 7.1 | RHEL 7.2 |
|---|---|---|---|---|---|
Installers
| Ubuntu 14.04 | Windows x64 | Windows x86 | Mac OS X | CentOS 7.1 | RHEL 7.2 | |
|---|---|---|---|---|---|---|
| Version |  |
 |
 |
 |
 |
 |
| Installers | Download Debian Package | Download Installer | Download Installer | Download Pkg | N/A | N/A |
| Binaries | Download tar file | Download zip file | Download zip file | Download tar file | Download tar file | Download tar file |
Interested in .NET Core + ASP.NET Core 1.0 RC1 bits?
This toolchain is independent from the DNX-based .NET Core + ASP.NET Core 1.0 RC1 bits. If you are looking for .NET Core + ASP.NET Core 1.0 RC1 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]/[rid]/[binary name] that you can just 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.
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.