Editing Choco
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 9: | Line 9: | ||
Please run '[[choco -?]]' or 'choco <command> -?' for help menu. | Please run '[[choco -?]]' or 'choco <command> -?' for help menu. | ||
| − | == [[ | + | == Installation == |
| + | [[Set-ExecutionPolicy]] Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1')) | ||
| + | .../... | ||
| + | Chocolatey (choco.exe) is now ready. | ||
| + | You can call choco from anywhere, command line or powershell by typing choco. | ||
| + | Run choco /? for a list of functions. | ||
| + | You may need to shut down and restart powershell and/or consoles | ||
| + | first prior to using choco. | ||
| + | Ensuring Chocolatey commands are on the path | ||
| + | Ensuring chocolatey.nupkg is in the lib folder | ||
| + | |||
| + | |||
| + | <pre> | ||
| + | cocho | ||
| + | cocho : The term 'cocho' 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 | ||
| + | + cocho | ||
| + | + ~~~~~ | ||
| + | + CategoryInfo : ObjectNotFound: (cocho:String) [], CommandNotFoundException | ||
| + | + FullyQualifiedErrorId : CommandNotFoundException | ||
| + | </pre> | ||
| + | |||
== Related == | == Related == | ||
Advertising:
