Downloads of v 1.0.0-RC2:


Last Update:

20 May 2016

Package Maintainer(s):

Software Author(s):

  • Microsoft


dotnet .net .netcore dotnetcore SDK admin

.Net Core SDK

This is a prerelease version of .Net Core SDK.

  • 1
  • 2
  • 3

1.0.0-RC2 | Updated: 20 May 2016



Downloads of v 1.0.0-RC2:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
.Net Core SDK 1.0.0-RC2

This is a prerelease version of .Net Core SDK.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


To install .Net Core SDK, run the following command from the command line or from PowerShell:


To upgrade .Net Core SDK, run the following command from the command line or from PowerShell:


To uninstall .Net Core SDK, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade dotnetcoresdk -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade dotnetcoresdk -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure dotnetcoresdk installed
    name: dotnetcoresdk
    state: present
    version: 1.0.0-RC2
    source: STEP 3 URL

See docs at

chocolatey_package 'dotnetcoresdk' do
  action    :install
  version  '1.0.0-RC2'
  source   'STEP 3 URL'

See docs at

    Name: dotnetcoresdk,
    Version: 1.0.0-RC2,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller dotnetcoresdk
   Name     = 'dotnetcoresdk'
   Ensure   = 'Present'
   Version  = '1.0.0-RC2'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'dotnetcoresdk':
  provider => 'chocolatey',
  ensure   => '1.0.0-RC2',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install dotnetcoresdk version="1.0.0-RC2" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.

.NET Core is a set of runtime, library and compiler components. Microsoft uses these components in various configurations for device and cloud workloads. You can do the same for your app or service.
Managed runtimes make code easy to write and guarantee safe execution. .NET Core manages memory with a garbage collector, compiles your code with a JIT compiler or ahead of time with .NET Native.
You can create .NET Core apps that run on multiple OSes and CPUs. .NET Core runs on Windows. Ports are in progress for Linux, OS X and FreeBSD, as is integration with the LLVM compiler.
This package only supports x64 architecture.

# dotnetcoresdk-chocolatey
This is the source of chocolatey package for .Net Core SDK.
$packageName = 'DotNetCoreSDK'
$fileType = 'exe'
$silentArgs = '/quiet'
$url = ''
$version = '1.0.0.RC2'

function Test-RegistryValue {

param (



try {

    if (Test-Path -Path $Path) {
        Get-ItemProperty -Path $Path | Select-Object -ExpandProperty $Value -ErrorAction Stop | Out-Null
        return $true

catch {
    return $false


function CheckDotNetCliInstalled {

    $registryPath = 'HKLM:\SOFTWARE\Wow6432Node\dotnet\Setup\InstalledVersions\x64\sharedfx\Microsoft.NETCore.App'
    if (Test-RegistryValue -Path $registryPath -Value 1.0.0-rc2) {
        return $true

if (CheckDotNetCliInstalled) {
    Write-Host "Microsoft .Net Core SDK is already installed on your machine."
elseif (Get-ProcessorBits(32)){
    throw "32 bit Microsoft .Net Core SDK is not available."
else {
	Install-ChocolateyPackage $packageName $fileType $silentArgs '' $url

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
.Net Core SDK 1.0.0-RC2 445 Friday, May 20, 2016 Exempted

This package has no dependencies.

Discussion for the .Net Core SDK Package

Ground Rules:

  • This discussion is only about .Net Core SDK and the .Net Core SDK package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or .Net Core SDK, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus