Rewrite

[ethanbergstrom]

Refactor of the module with several feature additions

Added

• Searching/installing/managing multiple Chocolatey sources (Is there a way to set ChocolateyGet's package source as trusted? #5)
• DSC Compatibility, including additional package arguments
• 'Upgrade' packages using the 'latest' required version keyword (No concept of 'upgrades' #14)
  • Thanks to @matthewprenger for help with this
• Package and Choco.exe installation can run without confirmation prompts by passing the -AcceptLicense flag (No support for -AcceptLicense flag #17)
  • Thanks to @Gregoorio for the idea
• Support for CoreCLR-based PowerShell (7.0.1 or higher) (PowerShell 7 support #18)
  • Thanks to @sgryphon for bringing this up
• Availability via PSGallery on CoreCLR-based PowerShell (PowerShell 7 support #18)

Changed

• To facilitate readability, broke up main module file into several function files
  • Grouped by 'public' functions used by PackageManagement vs 'private' functions that contain much of the shared logic for interacting with Chocolatey
  • Common logic, such as building commands, sending them to Chocolatey, and parsing results, are consolidated across multiple PackageManagement cmdlets into a single set of helper functions
• Choco.exe installed automatically without any user prompts if -Force flag is passed
• Uninstall behavior to also remove all unnecessary dependencies
• Invokes Chocolatey via native API by default under PowerShell 5.1 and below for significant performance gains
  • Thanks to @jirkapok for the inspiration

Fixed

• Get-Package no longer lists 'chocolatey' twice (Get-Package lists chocolatey twice #12)
• Improved performance when downloading large packages with embedded installers
• Choco.exe once again installs automatically after TLS 1.2 changes to chocolatey.org (Choco.exe doesn't install automatically due to TLS 1.2 changes #16)
  • Thanks to @kendr1ck for help with this
• Suppress Choco prompts during uninstall and upgrade actions

Removed

• With Chocolatey-managed upgrades via the provider now available, the package provider no longer unilaterally upgrades Chocolatey on invocation if already installed
• No longer displays progress bars in order to simplify passing data between functions via the pipeline in a way that's idiomatic to PowerShell

[ethanbergstrom]

@jianyunt would you be willing to give this a review? I've run out of ideas for contributions :)

I'm not listed as a project collaborator, so I cant formally add a review request to the PR.

Thanks!

[Gregoorio]

Hello @ethanbergstrom,

I saw that there was a new version 1.2.0 of Chocolatier. I don't know if anyone has tested adding their own repository via "register-packagesource" commands, but I get an error in the 'name' parameter (see below)

PS C:\Windows\system32> Register-PackageSource -name TEST -location https://myrepo/nuget -provider Chocolatier -Trusted

WARNING: MSG:UnableToDownload «https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409» «»
WARNING: Unable to download the list of available providers. Check your internet connection.
Register-PackageSource : Cannot bind argument to parameter 'name' because it is an empty string.
At line:1 char:1

• Register-PackageSource -name TEST -location https://myrepo ...

•   + CategoryInfo          : InvalidData: (Microsoft.Power...erPackageSource:RegisterPackageSource) [Register-PackageSource], Exception
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,New-PackageSource,Microsoft.PowerShell.PackageManagement.Cmdlets.RegisterPackageSour 
   ce
  
  

Can you confirm. Do you have that the same problem?
Is this a mistake on the side of the new provider Chocolatier 1.2.0 ?

This problem does not occur in a e.g. 1.0.4 Chocolatier version.

[ethanbergstrom]

Hey @Gregoorio,

I opened up a new issue on your behalf over on the Chocolatier project.