Downloads of v


Last Update:

03 Mar 2017

Package Maintainer(s):

Software Author(s):

  • johnypony3


nuget bundler F# admin


This is a prerelease version of Paket.

  • 1
  • 2
  • 3 | Updated: 03 Mar 2017



Downloads of v



Software Author(s):

  • johnypony3

  • 1
  • 2
  • 3

This is a prerelease version of Paket.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


To install Paket, run the following command from the command line or from PowerShell:


To upgrade Paket, run the following command from the command line or from PowerShell:


To uninstall Paket, 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 paket -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 paket -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 paket installed
    name: paket
    state: present
    source: STEP 3 URL

See docs at

chocolatey_package 'paket' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: paket,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller paket
   Name     = 'paket'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'paket':
  provider => 'chocolatey',
  ensure   => '',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install paket version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

There are versions of this package awaiting moderation . See the Version History section below.

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

A dependency manager for .NET with support for NuGet packages and Git repositories.

$ErrorActionPreference = 'Stop';

$versionPath = Join-Path -Path $PSScriptRoot -ChildPath .version

$ogversion = Get-Content $versionPath

$paketInfo = Invoke-RestMethod -Uri ''
$repoInfo = $paketInfo | where { $_.tag_name -eq $ogversion }

$toolsDir = Join-Path -Path $ENV:chocolateyPackageFolder -ChildPath 'tools'

$repoInfo.assets | % {
    $fileNameFull = Join-Path -Path $toolsDir -ChildPath $
    Get-ChocolateyWebFile -PackageName $ENV:chocolateyPackageName -FileFullPath $fileNameFull -Url $_.browser_download_url

Install-ChocolateyEnvironmentVariable -VariableName "PaketExePath" -VariableValue "paket.exe" -VariableType Machine
$ErrorActionPreference = 'Stop';

Install-ChocolateyEnvironmentVariable -VariableName "PaketExePath" -VariableValue $null -VariableType Machine

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
Paket 6.0.0-rc002 13 Monday, June 14, 2021 Exempted
Paket 6.0.0-rc001 35 Monday, May 3, 2021 Exempted
Paket 6.0.0-beta9 36 Tuesday, April 13, 2021 Approved
Paket 6.0.0-beta8 57 Sunday, December 13, 2020 Approved
Paket 6.0.0-beta7 22 Saturday, December 12, 2020 Approved
Paket 6.0.0-beta4 25 Thursday, December 3, 2020 Approved
Paket 6.0.0-beta3 27 Tuesday, November 24, 2020 Approved
Paket 6.0.0-beta2 28 Monday, November 23, 2020 Approved
Paket 6.0.0-beta11 13 Monday, May 3, 2021 Exempted
Paket 6.0.0-beta10 8 Friday, April 23, 2021 Exempted

Make Paket compatible with DotNet SDK preview3
Tail Recursive Package Resolution -
Reorganized resolver -
USABILITY: Added option to have paket restore fail on check failure -
Generate load scripts on install abidding to new paket.dependencies option -

This package has no dependencies.

Discussion for the Paket Package

Ground Rules:

  • This discussion is only about Paket and the Paket 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 Paket, 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