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
Livar 718b049ae9 Fixing test failure.
NuGet changed how they display the error message.
2017-06-01 21:31:14 -07:00
build Updated NuGet version for VS 15.3 preview3 release 2017-06-01 17:55:51 -07:00
build_projects Updating the runtime framework versions for 1.0.5 and 1.1.1 and updating the CLI branding to 1.0.4. 2017-04-24 18:11:59 -07:00
buildpipeline Temporarily use sandboxes for publishing 2017-02-03 12:09:55 -08:00
Documentation Dummy commit. 2017-05-04 13:25:26 -07:00
packaging Adding error code 1638 as a ignore/success error when installing the VC_Redist. 2017-04-06 15:11:57 -07:00
resources Return non-zero exit code for test failure in multitargeted test project. 2016-12-16 15:39:52 +05:30
scripts Fix case for variables we pass into docker. 2017-04-25 15:59:52 -05:00
src Updating the global.json creation to use the IFile interface and adding a unit test to cover it. 2017-05-22 09:51:30 -07:00
test Fixing test failure. 2017-06-01 21:31:14 -07:00
TestAssets Trying to fix the opensuse42 test failure, where we tried to invoke a tool that target 1.0.4 where the 1.0 runtime is not available. 2017-05-18 09:10:06 -07:00
tools Pinning the stage0 to the last build out of rel/1.0.1 and adding a project to download 1.0 dependencies for test assets. 2017-05-17 21:06:42 -07: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
branchinfo.txt Updating the branding to rel/1.1.0 2017-05-17 16:00:49 -07:00
build.cmd Merge rel/1.0.0 into feature/msbuild. 2016-07-18 14:44:06 -05:00
build.proj Add a hostfxr container version, because even a 1.1.2 hostfxr is being binplaced in a 1.1.0 container. 2017-04-25 20:40:19 -07: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 Updating the branding to rel/1.1.0 2017-05-17 16:00:49 -07: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 Update dotnet-deb-tool-consumer to use the latest dotnet-deb-tool. 2017-02-22 21:34:22 -06:00
netci.groovy Add new platforms to netci.groovy 2017-02-22 15:13:02 -06:00
NuGet.Config Adding the web feed to nuget.config, as some packages failed to mirror and we need a build ASAP. 2017-05-01 19:38:37 -07:00
NuGet.master.config add readme 2015-10-08 14:41:04 -07:00
omnisharp.json Update omnisharp setting. Disable auto restore. 2016-03-27 12:12:57 -07:00
PULL_REQUEST_TEMPLATE add PR template 2016-05-03 14:15:14 -07:00
README.md Fix README.md table 2017-04-12 20:44:16 -07:00
run-build.ps1 Pinning the stage0 to the last build out of rel/1.0.1 and adding a project to download 1.0 dependencies for test assets. 2017-05-17 21:06:42 -07:00
run-build.sh Pinning the stage0 to the last build out of rel/1.0.1 and adding a project to download 1.0 dependencies for test assets. 2017-05-17 21:06:42 -07: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 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.0.1
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.