chocolatey
Chocolatey - think executables/application packages (like apt-get for Windows), not library packages. This is what the Chocolatey NuGet goodness is for. Chocolatey allows you to install application nuggets and run executables from anywhere. ||Executable Nuggets| For example, say you have an executable in the tools folder of your package named bob.exe. Then you can type 'chocolatey install yourPackageName [[-source] source] [[-version] version]' OR 'cinst yourPackageName [[-source] source] [[-version] version]' and when it finishes you can type 'bob' and it will run your application executable. ||Application Nuggets - Full on double rainbow|| For example, say you type 'chocolatey install 7zip [[-source] source] [[-version] version]' OR 'cinst 7zip [[-source] source] [[-version] version]' - when it finishes you will have installed 7zip on your machine (in your add/remove programs).
Install
dotnet add package chocolatey --version 0.9.3
Install-Package chocolatey -Version 0.9.3
<PackageReference Include="chocolatey" Version="0.9.3" />
Frameworks
No framework metadata available.
Dependencies
No declared dependencies.
Adoption guide
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.