extern/PowerShell
1
0
Fork 0
mirror of https://github.com/fleschutz/PowerShell.git synced 2025-04-29 13:14:49 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of github.com:fleschutz/PowerShell

Browse Source
This commit is contained in:
Markus Fleschutz 2022-10-28 09:25:49 +02:00
commit bbd7a6c36c
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Docs/FAQ.md
View File

@ -12,16 +12,16 @@ Why use PowerShell?
✔️ it's **cross-platform** - available for Linux, Mac OS and Windows
✔️ it's **open-source and free** - see the Github repository at https://github.com/PowerShell/PowerShell
✔️ it's **open-source and free** - see the Github repository at: https://github.com/PowerShell/PowerShell
✔️ it's **easy to learn** - see the tutorial for beginners at https://www.guru99.com/powershell-tutorial.html
✔️ it's **easy to learn** - see the tutorial for beginners at: https://www.guru99.com/powershell-tutorial.html
✔️ it's **fully documented** - see the official PowerShell documentation at https://docs.microsoft.com/en-us/powershell/
✔️ it's **fully documented** - see the PowerShell documentation at: https://docs.microsoft.com/en-us/powershell/
How to get PowerShell?
----------------------
* **On Windows** PowerShell is preinstalled. **However,** the default execution policy is "restricted" which disallows the execution of scripts! To change this, open the *Windows PowerShell (Administrator)* console and enter:
* **On Windows** PowerShell is preinstalled. **However,** the execution policy is 'restricted' by default! To allow script execution: open the *Windows PowerShell (Administrator)* console and enter:
```
PS> Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser
```
@ -42,7 +42,7 @@ How to get the PowerShell Scripts?
How to execute PowerShell Scripts?
----------------------------------
1. In the Windows desktop: right-click the script and select: *Execute with PowerShell*
2. In a command-line interface (CLI, e.g. *Windows Terminal*, either local or remote via SSH) by typing: `./NAME_OF_SCRIPT`.
2. In a command-line interface (CLI, e.g. *Windows Terminal*, either local or remote via SSH) by typing: `./<FILENAME_OF_SCRIPT>`.
3. By connecting a context menu item with a script.
4. By voice control, e.g. see repo [talk2windows](https://github.com/fleschutz/talk2windows) for more information.
5. By using automation software, e.g. [Jenkins](https://www.jenkins.io).