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
2017-03-03 11:13:41 -08:00
build Fixing ubuntu deb generation. 2017-03-03 11:13:41 -08:00
build_projects Merge remote-tracking branch 'refs/remotes/dotnet/master' 2017-03-02 23:49:01 -08:00
buildpipeline Switch Docker Hub repo being used to microsoft/dotnet-buildtools-prereqs 2017-03-02 10:36:55 -06:00
Documentation misspelling of targeting 2017-02-16 16:10:19 -05:00
packaging Moving as many of our test assets to netcoreapp2.0 as possible. I believe the only ones missing at the test packages, because tools always target 1.0. And the other ones are VSTestDotNetCore and VSTestXUnitDotNetCore, because we can't run tests on 2.0 yet. Or, when I tried it failed. I may came back to try this out later. 2017-03-02 17:41:21 -08:00
resources Return non-zero exit code for test failure in multitargeted test project. 2016-12-16 15:39:52 +05:30
scripts Merge branch 'rel/1.0.1' into merge_rel101_into_master 2017-03-01 20:50:42 -08:00
src Merge remote-tracking branch 'refs/remotes/dotnet/master' 2017-03-02 23:49:01 -08:00
test Merge issues 2017-03-03 00:36:11 -08:00
TestAssets Merge issues 2017-03-03 00:36:11 -08:00
tools Standardize on newline between Property|ItemGroup areas 2017-03-02 20:38:56 -08:00
.cliversion Change stage0PJ version to preview2.1, which supports the new platforms. 2017-02-22 15:13:02 -06:00
.gitattributes merge my spike on compile/publish/run and switch from PS1 to C# 2015-10-06 10:46:43 -07:00
.gitignore add *.xproj.user to backup file types 2016-11-16 01:10:55 -08:00
.toolversions Update buildtools to 1.0.27-prerelease-01316-08 2017-02-22 15:13:02 -06:00
build.cmd Merge rel/1.0.0 into feature/msbuild. 2016-07-18 14:44:06 -05:00
build.proj merge 2017-02-14 16:43:23 -08: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
dir.props Move remaining Publish actions to redist.csproj 2017-03-01 00:45:02 -08:00
dir.tasks Bump MSBuild Version to 15.1.0-preview-000503-01 (#5199) 2017-01-05 14:56:11 -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 Remove MigrationDefaultsConstructor 2017-03-01 14:55:18 -08:00
netci.groovy Enable Jenkins to parse trx file 2017-03-02 11:26:19 -08:00
NuGet.Config Use the curated feed with all the relevant ASP.NET packages 2017-02-22 11:29:34 -08:00
NuGet.master.config add readme 2015-10-08 14:41:04 -07:00
PULL_REQUEST_TEMPLATE add PR template 2016-05-03 14:15:14 -07:00
README.md Merge branch 'rel/1.0.1' into merge_rel101_into_master 2017-03-01 20:50:42 -08:00
run-build.ps1 Add relative paths, add logs by default 2017-02-27 17:19:39 -08:00
run-build.sh Add relative paths, add logs by default 2017-02-27 17:19:39 -08: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 license text to LZMA SDK license notice 2017-02-26 12:11:05 -08: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.

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.

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

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 master
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 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

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.