New
#100
Kari, I was working through this today and ran into 1 problem which was easy to fix.
Step 3.2 saysThis 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:
Windows PowerShell
Copyright (C) 2015 Microsoft Corporation. All rights reserved.
Code:PS C:\Users\rrkurtz> Get-Packageprovider Name Version DynamicOptions ---- ------- -------------- Chocolatey 2.8.5.130 SkipDependencies, ContinueOnFailure, ExcludeVersion, ForceX86, PackageSave... msi 3.0.0.0 AdditionalArguments msu 3.0.0.0 NuGet 2.8.5.204 Destination, ExcludeVersion, Scope, Headers, FilterOnTag, Contains, AllowP... PowerShellGet 1.0.0.1 PackageManagementProvider, Type, Scope, InstallUpdate, PackageManagementPr... Programs 3.0.0.0 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?Code: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 + choco + ~~~~~ + CategoryInfo : ObjectNotFound: (choco:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
This is the error I get:
![]()