Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Learning-PowerShell-Names.md #4038

Merged
merged 1 commit into from
Mar 22, 2019
Merged

Update Learning-PowerShell-Names.md #4038

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions reference/docs-conceptual/learn/Learning-PowerShell-Names.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,9 @@ To list tasks running on DC01, you use the **/S** parameter and the computer nam
backslashes. For example, `tasklist /S DC01`.

> [!NOTE]
> Prior to PowerShell v6, `sc` was an alias for the `Set-Content` cmdlet. To run the **sc.exe**
> command, you must include the file extension.
> Prior to PowerShell v6, `sc` was an alias for the `Set-Content` cmdlet. Therefore, to run
> the **sc.exe** command in a version of PowerShell prior to v6, you must include the
> full filename **sc.exe** including the file extension **exe**.
Services and processes are examples of manageable elements on a computer that have well-defined
life cycles. You may start or stop services and processes, or get a list of all currently
Expand Down