Kari, I was working through this today and ran into 1 problem which was easy to fix.
Step 3.2 says
This did not happen for me. I had to add NuGet separately.
Notice that adding Chocolatey
, the provider NuGet
will also be added.
I opted to install ChocolateyGUI as a test and it installed fine but doesn't work at all. Looking at the ChocolateyGUI web page it says to do a choco update ChocolateyGUI. The choco command is not recognized by Powershell even though Chocolatey is installed:
Copyright (C) 2015 Microsoft Corporation. All rights reserved.
PS C:\Users\rrkurtz> Get-Packageprovider
Name Version DynamicOptions
---- ------- --------------
Chocolatey 184.108.40.206 SkipDependencies, ContinueOnFailure, ExcludeVersion, ForceX86, PackageSave...
msi 220.127.116.11 AdditionalArguments
NuGet 18.104.22.168 Destination, ExcludeVersion, Scope, Headers, FilterOnTag, Contains, AllowP...
PowerShellGet 22.214.171.124 PackageManagementProvider, Type, Scope, InstallUpdate, PackageManagementPr...
Programs 126.96.36.199 IncludeWindowsInstaller, IncludeSystemComponent
Is there a better place to ask about this since it doesn't really have anything to do with PowerShell PackageManagement. Or is there a way to do the update via PowerShell PackageManagement instead of chocolatey?
PS C:\Users\rrkurtz> choco
choco : The term 'choco' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ CategoryInfo : ObjectNotFound: (choco:String) , CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
This is the error I get: