Support Chocolatey as a 1st Class Deployment Mechanism

The 2.0 Preview 2 SDK is not available on chocolatey. The chocolatey package exists but is maintained by the community which means some packages are not available or take time to become available. Microsoft should support the chocolatey package as a first class deployment mechanism (Octopus Deploy are great at doing this). I want to be able to do:

choco install dotnet-sdk --version 1.0.4

Chocolatey is a standard release mechanism on Windows these days. It’s pre-installed on AppVeyor and would make obtaining the .NET Core SDK smoother.

The current mechanisms for installing the SDK are to download a non-standard PowerShell script then execute it. While this is great, it’s not discoverable (someone pointed this script out to me).

[devlead]

Kinda surprised Microsoft don’t want to own their bits, with recent influx of security patches it would’ve been nice if Chocolatey packages was a first class citizen part of your release pipeline. Authoriting a package isn’t hard, easy to automate and would be a great service to your customers. Many use Chocolatey as part of their orchestration / devops pipeline with private feeds. Know you’ve got your obtain ps/sh scripts but those don’t work in a locked down environment.

[dracan]

Definitely, +1 for this. Chocolatey is very popular, and it’s extremely frustrating when packages on there aren’t part of the original project’s deployment pipeline, meaning that the Chocolatey packages can’t be relied upon as being up to date. As @devlead said, it’s not hard to automate it - then it can just be handled automatically, and everyone who uses Chocolatey can trust that this is the latest version. Also, having Microsoft as the owner increases everyone’s confidence in the package.