Downloads of v 2.1.700:


Last Update:


Package Maintainer(s):

Software Author(s):

  • Microsoft


dotnetcore admin dotnet .net core sdk cli


This is not the latest version of .NET Core SDK available.

2.1.700 | Updated: 5/22/2019



Downloads of v 2.1.700:


Software Author(s):

  • Microsoft

.NET Core SDK 2.1.700

This is not the latest version of .NET Core SDK available.

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Validation Testing Passed

Verification Testing Exempt:

Dependencies require reboot.

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 dotnetcore-sdk -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 dotnetcore-sdk -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 dotnetcore-sdk installed
    name: dotnetcore-sdk
    state: present
    version: 2.1.700
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'dotnetcore-sdk' do
  action    :install
  version  '2.1.700'
  source   'STEP 3 URL'

See docs at

    Name: dotnetcore-sdk,
    Version: 2.1.700,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller dotnetcore-sdk
   Name     = 'dotnetcore-sdk'
   Ensure   = 'Present'
   Version  = '2.1.700'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'dotnetcore-sdk':
  provider => 'chocolatey',
  ensure   => '2.1.700',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install dotnetcore-sdk version="2.1.700" 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 was approved by moderator gep13 on 5/25/2019.


.NET Core is a blazing fast, lightweight and modular platform for creating web applications and services that run on Windows, Linux and Mac.

The SDK includes the runtime and command line tools for creating .NET Core applications


$ErrorActionPreference = 'Stop';

$packageName= 'dotnetcore-sdk'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''
$checksum   = 'AD03A18C19DC8F5D4E2FB1DF3DE46BCA1249912416791B02F504A3E221E49D360A216CD059FCF696F9719A4340AE3CCA43CAC6B6433E014D559FDA635FC8BC1E'
$url64      = ''
$checksum64 = '472DFBC269BE021D01D0479C1EC0FF1FA5F34D78907C69DEA0076C57D2E98E85004619C9B282C0C3FDBA7831775F6A955B8FF86A00163CE1C5941A4FECFFA1A0'

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'EXE'
  url           = $url
  url64bit      = $url64

  silentArgs    = "/install /quiet /norestart /log `"$env:TEMP\$($packageName)\$($packageName).MsiInstall.log`""
  validExitCodes= @(0, 3010, 1641)

  softwareName  = 'dotnet-core*'
  checksum      = $checksum
  checksumType  = 'SHA512'
  checksum64    = $checksum64

Install-ChocolateyPackage @packageArgs

$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Microsoft .NET Core SDK*'
  fileType      = 'EXE'
  silentArgs    = "/uninstall /quiet"
  validExitCodes= @(0, 3010, 1605, 1614, 1641)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName'] | 
    ?{ -Not $_.WindowsInstaller -eq 1 } # for some reason the SDK is registered twice but picking the EXE instead of MSI here

if ($key.Count -eq 1) {
  $key | % { 
    $file = $_.UninstallString -replace '(?<=".+")\s+.*$', ''
    Write-Output "File: $file"
    $packageArgs['file'] = $file

    Uninstall-ChocolateyPackage @packageArgs
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}

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 3.0.100-rc1-014190 1016 Tuesday, September 17, 2019 Approved
.NET Core SDK 3.0.100-preview9-014004 1932 Thursday, September 5, 2019 Approved
.NET Core SDK 3.0.100-preview8-013656 2571 Wednesday, August 14, 2019 Approved
.NET Core SDK 3.0.100-preview7-012821 1949 Tuesday, July 23, 2019 Approved
.NET Core SDK 3.0.100-preview6-012264 1929 Wednesday, June 12, 2019 Approved
.NET Core SDK 3.0.100-preview5-011568 974 Monday, May 6, 2019 Approved
.NET Core SDK 3.0.100-preview4-011223 380 Friday, April 19, 2019 Approved
.NET Core SDK 3.0.100-preview3-010431 609 Thursday, March 7, 2019 Approved
.NET Core SDK 3.0.100-preview-010184 98 Friday, March 1, 2019 Approved

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