Downloads of v 5.0.0-alpha007:


Last Update:

28 Apr 2017

Package Maintainer(s):

Software Author(s):

  • Paket team


nuget bundler F#


This is a prerelease version of Paket.PowerShell.

  • 1
  • 2
  • 3

5.0.0-alpha007 | Updated: 28 Apr 2017



Downloads of v 5.0.0-alpha007:



Software Author(s):

  • Paket team


nuget bundler F#

  • 1
  • 2
  • 3
Paket.PowerShell 5.0.0-alpha007

This is a prerelease version of Paket.PowerShell.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


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


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


To uninstall Paket.PowerShell, 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.powershell -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.powershell -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.powershell installed
    name: paket.powershell
    state: present
    version: 5.0.0-alpha007
    source: STEP 3 URL

See docs at

chocolatey_package 'paket.powershell' do
  action    :install
  version  '5.0.0-alpha007'
  source   'STEP 3 URL'

See docs at

    Name: paket.powershell,
    Version: 5.0.0-alpha007,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller paket.powershell
   Name     = 'paket.powershell'
   Ensure   = 'Present'
   Version  = '5.0.0-alpha007'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'paket.powershell':
  provider => 'chocolatey',
  ensure   => '5.0.0-alpha007',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install paket.powershell version="5.0.0-alpha007" 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 as a trusted package on 28 Apr 2017.


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

$tools = "$env:chocolateyPackageFolder\tools"
. "$tools\Install-PSModulePath.ps1"
Install-PSModulePath -pathToInstall $tools -pathType ([System.EnvironmentVariableTarget]::Machine)
param($installPath, $toolsPath, $package)
Import-Module (Join-Path $toolsPath 'Paket.PowerShell\Paket.PowerShell.psd1') -DisableNameChecking
# Copyright 2011 - Present RealDimensions Software, LLC & original authors/contributors from
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# See the License for the specific language governing permissions and
# limitations under the License.

function Install-PSModulePath {
  [string] $pathToInstall,
  [System.EnvironmentVariableTarget] $pathType = [System.EnvironmentVariableTarget]::User
  Write-Debug "Running 'Install-PSModulePath' with pathToInstall:`'$pathToInstall`'";
  $originalPathToInstall = $pathToInstall

  #get the PSModulePath variable
  $envPath = $env:PSModulePath
  if (!$envPath.ToLower().Contains($pathToInstall.ToLower()))
    Write-Host "PSModulePath environment variable does not have $pathToInstall in it. Adding..."
    $actualPath = Get-EnvironmentVariable -Name 'PSModulePath' -Scope $pathType

    $statementTerminator = ";"
    #does the path end in ';'?
    $hasStatementTerminator = $actualPath -ne $null -and $actualPath.EndsWith($statementTerminator)
    # if the last digit is not ;, then we are adding it
    If (!$hasStatementTerminator -and $actualPath -ne $null) {$pathToInstall = $statementTerminator + $pathToInstall}
    if (!$pathToInstall.EndsWith($statementTerminator)) {$pathToInstall = $pathToInstall + $statementTerminator}
    $actualPath = $actualPath + $pathToInstall

    if ($pathType -eq [System.EnvironmentVariableTarget]::Machine) {
      if (Test-ProcessAdminRights) {
        Set-EnvironmentVariable -Name 'PSModulePath' -Value $actualPath -Scope $pathType
      } else {
        $psArgs = "Install-PSModulePath -pathToInstall `'$originalPathToInstall`' -pathType `'$pathType`'"
        Start-ChocolateyProcessAsAdmin "$psArgs"
    } else {
      Set-EnvironmentVariable -Name 'PSModulePath' -Value $actualPath -Scope $pathType

    #add it to the local path as well so users will be off and running
    $envPSPath = $env:PSModulePath
    $env:PSModulePath = $envPSPath + $statementTerminator + $pathToInstall

# [System.Text.RegularExpressions.Regex]::Match($Path,[System.Text.RegularExpressions.Regex]::Escape('locationtoMatch') + '(?>;)?', '', [System.Text.RegularExpressions.RegexOptions]::IgnoreCase)


function createCompletionResult([string]$text, [string]$value, [string]$tooltip) {
    if ([string]::IsNullOrEmpty($value)) { return }
    if ([string]::IsNullOrEmpty($text)) { $text = $value }
    if ([string]::IsNullOrEmpty($tooltip)) { $tooltip = $value }
    $completionText = @{$true="'$value'"; $false=$value  }[$value -match "\W"]
    $completionText = $completionText -replace '\[', '``[' -replace '\]', '``]'
    New-Object System.Management.Automation.CompletionResult $completionText, $text, 'ParameterValue', $tooltip | write

$findPackages = {
    param($commandName, $parameterName, $wordToComplete, $commandAst, $fakeBoundParameter)
    Paket-FindPackages -SearchText $wordToComplete -Max 100 | % {
        createCompletionResult $_ $_ $_ | write

$findPackageVersions = {
    param($commandName, $parameterName, $wordToComplete, $commandAst, $fakeBoundParameter)
    if (-not $fakeBoundParameter.NuGet){ return }
    Paket-FindPackageVersions -Name $fakeBoundParameter.NuGet -Max 100 | % {
        createCompletionResult $_ $_ $_ | write

$showInstalledPackages = {
    param($commandName, $parameterName, $wordToComplete, $commandAst, $fakeBoundParameter)
    Paket-ShowInstalledPackages | % {
		$name = $_.Name
        createCompletionResult $name $name $name | write

# create and add $global:options to the list of completers
if (-not $global:options) { $global:options = @{CustomArgumentCompleters = @{};NativeArgumentCompleters = @{}}}

$global:options['CustomArgumentCompleters']['Paket-Add:NuGet'] = $findPackages
$global:options['CustomArgumentCompleters']['Paket-Add:Version'] = $findPackageVersions
$global:options['CustomArgumentCompleters']['Paket-Update:NuGet'] = $showInstalledPackages
$global:options['CustomArgumentCompleters']['Paket-Update:Version'] = $findPackageVersions
$global:options['CustomArgumentCompleters']['Paket-Remove:NuGet'] = $showInstalledPackages
$global:options['CustomArgumentCompleters']['Paket-FindPackageVersions:Name'] = $findPackages
$global:options['CustomArgumentCompleters']['Paket-FindRefs:NuGet'] = $showInstalledPackages

$function:tabexpansion2 = $function:tabexpansion2 -replace 'End\r\n{','End { if ($null -ne $options) { $options += $global:options} else {$options = $global:options}'
md5: 294022B1CA03D0E9D8C2FB30145D8D64 | sha1: D44A97BA36EA787D57CB5CDD27AC276122DF760B | sha256: DB5467F7DF70ABF0907D7B94A7A6741E91DB92934A316598438E38238F6E4FD8 | sha512: DFC79014A0AE52453364F19C5811884B6F413363E9E23ADDCCF4837396CF8D098B73267EBD7EC62139109D1D5039C1F39187A62C6C5859A90A25C33BD2FF66D8
GUID = 'e7bdf748-93e9-4e24-95a2-ace98df3d687'
Author = 'Paket'
Copyright = '(c) 2015 Paket. All rights reserved.'
PowerShellVersion = '3.0'
CLRVersion = '4.0'
RootModule = 'Paket.PowerShell.dll'
HelpInfoUri = ''
ScriptsToProcess = 'ArgumentTabCompletion.ps1'
# the build will append these lines
# ModuleVersion = '1.0.0'
# }
ModuleVersion = '5.0.0'

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.PowerShell 5.0.0-alpha007 573 Friday, April 28, 2017 Approved
Paket.PowerShell 5.0.0-alpha006 308 Friday, April 28, 2017 Approved
Paket.PowerShell 5.0.0-alpha005 324 Thursday, April 27, 2017 Approved
Paket.PowerShell 5.0.0-alpha004 360 Thursday, April 27, 2017 Approved
Paket.PowerShell 5.0.0-alpha003 290 Thursday, April 27, 2017 Approved
Paket.PowerShell 5.0.0-alpha002 324 Thursday, April 27, 2017 Approved
Paket.PowerShell 5.0.0-alpha001 334 Thursday, April 27, 2017 Approved
Paket.PowerShell 4.8.7 315 Friday, June 2, 2017 Approved
Paket.PowerShell 4.8.6 325 Tuesday, May 23, 2017 Approved

BUGFIX: Fixed dotnetcore integration:
Paket now properly understands runtime and reference assemblies
Paket now understands the runtime graph and restores runtime dependencies
New API InstallModel.GetRuntimeAssemblies and InstallModel.GetRuntimeLibraries can be used to retrieve the correct assets for a particular RID and TFM
New command paket generate-nuspec
BUGFIX: Paket now accepts multiple nuspec files in fix-nuspec -
BUGFIX: Improved C++ support
BUGFIX: Fixed bug with ignored argument of getPackageDetails -
BUGFIX: HTTP dependency - strip query string to detect a file name -
BUGFIX: Proper encoding "+" in package download url -
BUGFIX: Paket failed when group is removed (or renamed) -
BUGFIX: Filter .targets / .props earlier -
BREAKING CHANGE: InstallModel API changed and Paket.Core.dll users might need to adapt
USABILITY: Don't let build continue when paket failed -

This package has no dependencies.

Discussion for the Paket.PowerShell Package

Ground Rules:

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