profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/chasewilson/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Chase Wilson chasewilson @Microsoft

chasewilson/SchemaExtensionDsc 1

Intakes .LDF files and allows DSC to extend the Active Directory Schema using the LDIFDE tool

chasewilson/SqlServerDsc 1

This module contains DSC resources for deployment and configuration of SQL Server.

chasewilson/azure-devops-docs 0

This repo is the home of the official Azure DevOps documentation for Microsoft. GitHub Issues filed in this repository should be for problems with the documentation.

chasewilson/dsccommunity.org 0

DSC community organisation's website

chasewilson/dscpush 0

DSC Push is a Class-based PowerShell DSC Configuration management framework

chasewilson/pipelines-dotnet-core 0

A simple ASP.NET Core MVC app for Azure Pipelines docs

chasewilson/pipelines-java 0

Sample Java application referred to by Azure Pipelines documentation

PR opened MicrosoftDocs/PowerShell-Docs

Automatically committed changes.

PR Summary

<!-- Summarize your changes and list related issues here -->

PR Context

<!-- There is a numbered folder for each version of the PowerShell cmdlet content. Changes to cmdlet reference should be made to all versions where applicable. The /docs-conceptual folder tree does not have version folders. --> Fixes #8131 Fixes AB#1880290

Select the area of the Table of Contents containing the documents being changed.

Conceptual content

  • [ ] Overview and Install
  • [ ] Learning PowerShell
    • [ ] PowerShell 101
    • [ ] Deep dives
    • [ ] Sample scripts
    • [ ] Remoting
  • [ ] Release notes (What's New)
  • [ ] Windows PowerShell
    • WMF, ISE, release notes, etc.
  • [ ] DSC articles
  • [ ] Community resources
  • [ ] Gallery articles
  • [ ] Scripting and development
    • [ ] Language Spec
    • [ ] Legacy SDK

Cmdlet reference & about_ topics

  • [x] Preview content
  • [x] Version 7.1 content
  • [x] Version 7.0 content
  • [x] Version 5.1 content

PR Checklist

  • [x] I have read the contributors guide and followed the style and process guidelines
  • [x] PR has a meaningful title
  • [x] PR is targeted at the staging branch
  • [x] All relevant versions updated
  • [x] Includes content related to issues and PRs - see Closing issues using keywords.
  • [x] This PR is ready to merge and is not Work in Progress
    • If the PR is work in progress, please add the prefix WIP: or [WIP] to the beginning of the title and remove the prefix when the PR is ready.
+236 -128

0 comment

8 changed files

pr created time in 16 hours

push eventchasewilson/PowerShell-Docs

chasewilson

commit sha 307f7aae6e87e26d4bebb006a88191d683dfaec8

Automatically committed changes.

view details

push time in 17 hours

create barnchchasewilson/PowerShell-Docs

branch : chasewilson-ghi8131

created branch time in 17 hours

push eventchasewilson/PowerShell-Docs

Chase Wilson

commit sha 9182e869a8ef28d2bb5c16d4cda58a85905f15df

No Linked Issue - Updates about_Parameter_Sets (#8114) * Automatically committed changes. * Apply suggestions from code review Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com> Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com>

view details

Sean Wheeler

commit sha 8d71dfccfdb038c685f6f34255b76fbc6469d853

Fixes #8116 - Replace parameter alias with actual name (#8117) * Replace parameter alias with actual name * fix typo

view details

Sean Wheeler

commit sha 2f550ccea99d505f1b2b99de94dffe247dfa73fe

File renames and moves for 7.2 release (#8118) * File renames and moves for 7.2 release * fix build errors * more build fixes * Update macOS card on landing page

view details

Sean Wheeler

commit sha ab7972d4e330573913ca0dcde4af4b2dca7c06a6

Update file list for experimental feature (#8119)

view details

Sean Wheeler

commit sha cb8ea1a736229117dc7d9cfc9e748344198243cc

Update redirects for get-verb (#8123)

view details

Sean Wheeler

commit sha 5049827df94b6d869aeb9ba3b74d1d02cfcb8b58

Add note about external commands (#8125)

view details

Sean Wheeler

commit sha 11ff31f25e7a84b110a11717913e7a209c6859bd

Use PSObject() constructor in stead of AsPSObject (#8127)

view details

Sean Wheeler

commit sha 84686d0555d40182f07e7965f3ceb00d27e27a5a

Use AsPSObject() to avoid nesting PSObjects (#8130)

view details

RaghuRocks3

commit sha 35710d8138dce057a842e8483c7da4bff5516f12

Update Export-Csv.md (#8128)

view details

Sean Wheeler

commit sha 4c33cdb977a61443a7ab4c6d8a769f546555b30c

Update PSReadLine and create Security Features doc (#8129) * Update PSReadLine and create Security Features doc * Apply suggestions from code review Co-authored-by: Chase Wilson <31453523+chasewilson@users.noreply.github.com> Co-authored-by: Chase Wilson <31453523+chasewilson@users.noreply.github.com>

view details

push time in 17 hours

Pull request review commentMicrosoftDocs/PowerShell-Docs

Update PSReadLine and create Security Features doc

+---+description: PowerShell has several features designed to improve the security of your scripting environment.+ms.date: 09/23/2021+title: PowerShell security features+---+# PowerShell security features++PowerShell has several features designed to improve the security of your scripting environment.++## Execution policy++PowerShell's execution policy is a safety feature that controls the conditions under which+PowerShell loads configuration files and runs scripts. This feature helps prevent the execution of+malicious scripts. You can use a Group Policy setting to set execution policies for computers and+users. Execution policies only apply to the Windows platform.++For more information see [about_Execution_Policies][exe-policy].++## Module and script block logging++Module Logging allows you to enable logging for selected PowerShell modules. The setting is+effective in all sessions on the computer. The pipeline execution events for the specified modules+are recorded in the Windows PowerShell log in Event Viewer.
Module Logging allows you to enable logging for selected PowerShell modules. This setting is
effective in all sessions on the computer. Pipeline execution events for the specified modules
are recorded in the Windows PowerShell log in Event Viewer.

MInor changes for easier reading and a question: Is it only the Windows PowerShell log the correct location for all versions?

sdwheeler

comment created time in 20 hours

Pull request review commentMicrosoftDocs/PowerShell-Docs

Update PSReadLine and create Security Features doc

+---+description: PowerShell has several features designed to improve the security of your scripting environment.+ms.date: 09/23/2021+title: PowerShell security features+---+# PowerShell security features++PowerShell has several features designed to improve the security of your scripting environment.++## Execution policy++PowerShell's execution policy is a safety feature that controls the conditions under which+PowerShell loads configuration files and runs scripts. This feature helps prevent the execution of+malicious scripts. You can use a Group Policy setting to set execution policies for computers and+users. Execution policies only apply to the Windows platform.++For more information see [about_Execution_Policies][exe-policy].++## Module and script block logging++Module Logging allows you to enable logging for selected PowerShell modules. The setting is+effective in all sessions on the computer. The pipeline execution events for the specified modules+are recorded in the Windows PowerShell log in Event Viewer.++Script Block Logging allows you to enable logging for the processing of commands, script blocks,+functions, and scripts - whether invoked interactively, or through automation. This information is+logged to the **Microsoft-Windows-PowerShell/Operational** event log.++For more information, see the following articles:++- [about_Group_Policy_Settings][logging]+- [about_Logging_Windows][log-win]+- [about_Logging_Non-Windows][log-unix]++## Constrained language mode++**ConstrainedLanguage** mode protects you system by the cmdlets and the .NET types that can be used+in a PowerShell session. For a full description, see [about_Language_Modes][lang-modes].++## Application Control++Windows 10 includes two technologies, [Windows Defender Application Control (WDAC)][WDAC] and+[AppLocker][applocker] that can be used for application control. They allow you to create a lockdown+experience to meet your organization's specific scenarios and requirements.++> [!NOTE]+> When it comes to [choosing between WDAC or AppLocker][choosing] it is generally recommended that+> customers implement application control using WDAC rather than AppLocker. WDAC is undergoing+> continual improvements and will be getting added support from Microsoft management platforms.+> Although AppLocker will continue to receive security fixes, it will not undergo new feature+> improvements.++**WDAC** was introduced with Windows 10 and allows organizations to control which drivers and+applications are allowed to run on their Windows 10 devices. WDAC is designed as a security feature+under the servicing criteria defined by the Microsoft Security Response Center (MSRC).++**AppLocker** builds on the application control features of Software Restriction Policies.+AppLocker contains new capabilities and extensions that allow you to create rules to allow or deny+apps from running based on unique identities of files and to specify which users or groups can run+those apps.++### Security Servicing Criteria++PowerShell follows the [Microsoft Security Servicing Criteria for Windows][mssec].+The table below outlines the features that meet the servicing criteria and those that do not.++|                  Feature                   |       Type       |+| ------------------------------------------ | ---------------- |+| System Lockdown - with WDAC                | Security Feature |+| Constrained language mode - with WDAC      | Security Feature |+| System Lockdown - with AppLocker           | Defense in Depth |+| Constrained language mode - with AppLocker | Defense in Depth |+| Execution Policy                           | Defense in Depth |++> [!NOTE]+> There is a corner-case scenario in AppLocker where you only have **Deny** rules and constrained+> language mode is not used to enforce the policy that allowed you to bypass the execution policy.+> Beginning in PowerShell 7.2, a change was made to ensure that AppLocker rules would take+> precedence over a `Set-ExecutionPolicy -ExecutionPolicy Bypass` command.
> Beginning in PowerShell 7.2, a change was made to ensure AppLocker rules take precedence
> over a `Set-ExecutionPolicy -ExecutionPolicy Bypass` command.
sdwheeler

comment created time in 20 hours

Pull request review commentMicrosoftDocs/PowerShell-Docs

Update PSReadLine and create Security Features doc

+---+description: PowerShell has several features designed to improve the security of your scripting environment.+ms.date: 09/23/2021+title: PowerShell security features+---+# PowerShell security features++PowerShell has several features designed to improve the security of your scripting environment.++## Execution policy++PowerShell's execution policy is a safety feature that controls the conditions under which+PowerShell loads configuration files and runs scripts. This feature helps prevent the execution of+malicious scripts. You can use a Group Policy setting to set execution policies for computers and+users. Execution policies only apply to the Windows platform.++For more information see [about_Execution_Policies][exe-policy].++## Module and script block logging++Module Logging allows you to enable logging for selected PowerShell modules. The setting is+effective in all sessions on the computer. The pipeline execution events for the specified modules+are recorded in the Windows PowerShell log in Event Viewer.++Script Block Logging allows you to enable logging for the processing of commands, script blocks,+functions, and scripts - whether invoked interactively, or through automation. This information is+logged to the **Microsoft-Windows-PowerShell/Operational** event log.++For more information, see the following articles:++- [about_Group_Policy_Settings][logging]+- [about_Logging_Windows][log-win]+- [about_Logging_Non-Windows][log-unix]++## Constrained language mode++**ConstrainedLanguage** mode protects you system by the cmdlets and the .NET types that can be used+in a PowerShell session. For a full description, see [about_Language_Modes][lang-modes].++## Application Control++Windows 10 includes two technologies, [Windows Defender Application Control (WDAC)][WDAC] and+[AppLocker][applocker] that can be used for application control. They allow you to create a lockdown+experience to meet your organization's specific scenarios and requirements.++> [!NOTE]+> When it comes to [choosing between WDAC or AppLocker][choosing] it is generally recommended that+> customers implement application control using WDAC rather than AppLocker. WDAC is undergoing+> continual improvements and will be getting added support from Microsoft management platforms.+> Although AppLocker will continue to receive security fixes, it will not undergo new feature+> improvements.++**WDAC** was introduced with Windows 10 and allows organizations to control which drivers and+applications are allowed to run on their Windows 10 devices. WDAC is designed as a security feature+under the servicing criteria defined by the Microsoft Security Response Center (MSRC).++**AppLocker** builds on the application control features of Software Restriction Policies.+AppLocker contains new capabilities and extensions that allow you to create rules to allow or deny+apps from running based on unique identities of files and to specify which users or groups can run+those apps.++### Security Servicing Criteria++PowerShell follows the [Microsoft Security Servicing Criteria for Windows][mssec].+The table below outlines the features that meet the servicing criteria and those that do not.++|                  Feature                   |       Type       |+| ------------------------------------------ | ---------------- |+| System Lockdown - with WDAC                | Security Feature |+| Constrained language mode - with WDAC      | Security Feature |+| System Lockdown - with AppLocker           | Defense in Depth |+| Constrained language mode - with AppLocker | Defense in Depth |+| Execution Policy                           | Defense in Depth |++> [!NOTE]+> There is a corner-case scenario in AppLocker where you only have **Deny** rules and constrained+> language mode is not used to enforce the policy that allowed you to bypass the execution policy.
> language mode is not used to enforce the policy that allows you to bypass the execution policy.
sdwheeler

comment created time in 20 hours

Pull request review commentMicrosoftDocs/PowerShell-Docs

Update PSReadLine and create Security Features doc

+---+description: PowerShell has several features designed to improve the security of your scripting environment.+ms.date: 09/23/2021+title: PowerShell security features+---+# PowerShell security features++PowerShell has several features designed to improve the security of your scripting environment.++## Execution policy++PowerShell's execution policy is a safety feature that controls the conditions under which+PowerShell loads configuration files and runs scripts. This feature helps prevent the execution of+malicious scripts. You can use a Group Policy setting to set execution policies for computers and+users. Execution policies only apply to the Windows platform.++For more information see [about_Execution_Policies][exe-policy].++## Module and script block logging++Module Logging allows you to enable logging for selected PowerShell modules. The setting is+effective in all sessions on the computer. The pipeline execution events for the specified modules+are recorded in the Windows PowerShell log in Event Viewer.++Script Block Logging allows you to enable logging for the processing of commands, script blocks,+functions, and scripts - whether invoked interactively, or through automation. This information is+logged to the **Microsoft-Windows-PowerShell/Operational** event log.
Script Block Logging enables logging for the processing of commands, script blocks,
functions, and scripts - whether invoked interactively, or through automation. This information is
logged to the **Microsoft-Windows-PowerShell/Operational** event log.

Same question as above. Is the location accurate for all versions?

sdwheeler

comment created time in 20 hours

Pull request review commentMicrosoftDocs/PowerShell-Docs

Update PSReadLine and create Security Features doc

+---+description: PowerShell has several features designed to improve the security of your scripting environment.+ms.date: 09/23/2021+title: PowerShell security features+---+# PowerShell security features++PowerShell has several features designed to improve the security of your scripting environment.++## Execution policy++PowerShell's execution policy is a safety feature that controls the conditions under which+PowerShell loads configuration files and runs scripts. This feature helps prevent the execution of+malicious scripts. You can use a Group Policy setting to set execution policies for computers and+users. Execution policies only apply to the Windows platform.++For more information see [about_Execution_Policies][exe-policy].++## Module and script block logging++Module Logging allows you to enable logging for selected PowerShell modules. The setting is+effective in all sessions on the computer. The pipeline execution events for the specified modules+are recorded in the Windows PowerShell log in Event Viewer.++Script Block Logging allows you to enable logging for the processing of commands, script blocks,+functions, and scripts - whether invoked interactively, or through automation. This information is+logged to the **Microsoft-Windows-PowerShell/Operational** event log.++For more information, see the following articles:++- [about_Group_Policy_Settings][logging]+- [about_Logging_Windows][log-win]+- [about_Logging_Non-Windows][log-unix]++## Constrained language mode++**ConstrainedLanguage** mode protects you system by the cmdlets and the .NET types that can be used+in a PowerShell session. For a full description, see [about_Language_Modes][lang-modes].
**ConstrainedLanguage** mode protects your system by constraining the cmdlets and .NET types that can be used
in a PowerShell session. For a full description, see [about_Language_Modes][lang-modes].
sdwheeler

comment created time in 20 hours

Pull request review commentMicrosoftDocs/PowerShell-Docs

Update PSReadLine and create Security Features doc

+---+description: PowerShell has several features designed to improve the security of your scripting environment.+ms.date: 09/23/2021+title: PowerShell security features+---+# PowerShell security features++PowerShell has several features designed to improve the security of your scripting environment.++## Execution policy++PowerShell's execution policy is a safety feature that controls the conditions under which+PowerShell loads configuration files and runs scripts. This feature helps prevent the execution of+malicious scripts. You can use a Group Policy setting to set execution policies for computers and+users. Execution policies only apply to the Windows platform.++For more information see [about_Execution_Policies][exe-policy].++## Module and script block logging++Module Logging allows you to enable logging for selected PowerShell modules. The setting is+effective in all sessions on the computer. The pipeline execution events for the specified modules+are recorded in the Windows PowerShell log in Event Viewer.++Script Block Logging allows you to enable logging for the processing of commands, script blocks,+functions, and scripts - whether invoked interactively, or through automation. This information is+logged to the **Microsoft-Windows-PowerShell/Operational** event log.++For more information, see the following articles:++- [about_Group_Policy_Settings][logging]+- [about_Logging_Windows][log-win]+- [about_Logging_Non-Windows][log-unix]++## Constrained language mode++**ConstrainedLanguage** mode protects you system by the cmdlets and the .NET types that can be used+in a PowerShell session. For a full description, see [about_Language_Modes][lang-modes].++## Application Control++Windows 10 includes two technologies, [Windows Defender Application Control (WDAC)][WDAC] and+[AppLocker][applocker] that can be used for application control. They allow you to create a lockdown+experience to meet your organization's specific scenarios and requirements.++> [!NOTE]+> When it comes to [choosing between WDAC or AppLocker][choosing] it is generally recommended that+> customers implement application control using WDAC rather than AppLocker. WDAC is undergoing+> continual improvements and will be getting added support from Microsoft management platforms.+> Although AppLocker will continue to receive security fixes, it will not undergo new feature+> improvements.++**WDAC** was introduced with Windows 10 and allows organizations to control which drivers and+applications are allowed to run on their Windows 10 devices. WDAC is designed as a security feature+under the servicing criteria defined by the Microsoft Security Response Center (MSRC).++**AppLocker** builds on the application control features of Software Restriction Policies.+AppLocker contains new capabilities and extensions that allow you to create rules to allow or deny
AppLocker contains new capabilities and extensions that enable you to create rules to allow or deny
sdwheeler

comment created time in 20 hours

PullRequestReviewEvent
PullRequestReviewEvent

push eventMicrosoftDocs/PowerShell-Docs

Sean Wheeler

commit sha 5049827df94b6d869aeb9ba3b74d1d02cfcb8b58

Add note about external commands (#8125)

view details

push time in 2 days

PR merged MicrosoftDocs/PowerShell-Docs

Fixes #8122 - Add note about external commands

PR Summary

<!-- Summarize your changes and list related issues here -->

Fixes AB#1879363 - Fixes #8122 - Add note about external commands

<!-- There is a numbered folder for each version of the PowerShell cmdlet content. Changes to cmdlet reference should be made to all versions where applicable. The /docs-conceptual folder tree does not have version folders. -->

Select the area of the Table of Contents containing the documents being changed.

Conceptual content

  • [ ] Overview and Install
  • [ ] Learning PowerShell
    • [ ] PowerShell 101
    • [ ] Deep dives
    • [ ] Sample scripts
    • [ ] Remoting
  • [ ] Release notes (What's New)
  • [ ] Windows PowerShell
    • WMF, ISE, release notes, etc.
  • [ ] DSC articles
  • [ ] Community resources
  • [ ] Gallery articles
  • [ ] Scripting and development
    • [ ] Language Spec
    • [ ] Legacy SDK

Cmdlet reference & about_ topics

  • [x] Preview content
  • [x] Version 7.1 content
  • [x] Version 7.0 content
  • [x] Version 5.1 content

PR Checklist

  • [x] I have read the contributors guide and followed the style and process guidelines
  • [x] PR has a meaningful title
  • [x] PR is targeted at the staging branch
  • [x] All relevant versions updated
  • [x] Includes content related to issues and PRs - see Closing issues using keywords.
  • [x] This PR is ready to merge and is not Work in Progress
    • If the PR is work in progress, please add the prefix WIP: or [WIP] to the beginning of the title and remove the prefix when the PR is ready.
+52 -4

1 comment

4 changed files

sdwheeler

pr closed time in 2 days

issue closedMicrosoftDocs/PowerShell-Docs

about_Quoting_Rules

This page doesnt address external commands at all.

For example, with Bash you could run a command like this no problem:

curl 'http://gram.com/query/?query=f5&variables={"code":"CThvvO","reel":true,"first":50,"after":""}'

but PowerShell ignores that single quotes have been used, and just goes ahead and destroys the command.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 2 days

89z
PullRequestReviewEvent

push eventchasewilson/PowerShell-Docs

Chase Wilson

commit sha c3f432e62993bdecc5d1894c714e5921a06cd56e

Apply suggestions from code review Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com>

view details

push time in 4 days

pull request commentMicrosoftDocs/PowerShell-Docs

Add to definition of parameter

@ironyman, Thanks for your feedback here. I've added some clarification in a PR here.

I think this clarifies what you are talking about here. feel free to reach out if you have any questions.

ironyman

comment created time in 4 days

PR opened MicrosoftDocs/PowerShell-Docs

No Linked Issue - Updates about_Parameter_Sets

PR Summary

Updates to clarify parameter set behavior

PR Context

No Linked issues No Linked Azure Work Items

Select the area of the Table of Contents containing the documents being changed.

Conceptual content

  • [ ] Overview and Install
  • [ ] Learning PowerShell
    • [ ] PowerShell 101
    • [ ] Deep dives
    • [ ] Sample scripts
    • [ ] Remoting
  • [ ] Release notes (What's New)
  • [ ] Windows PowerShell
    • WMF, ISE, release notes, etc.
  • [ ] DSC articles
  • [ ] Community resources
  • [ ] Gallery articles
  • [ ] Scripting and development
    • [ ] Language Spec
    • [ ] Legacy SDK

Cmdlet reference & about_ topics

  • [x] Preview content
  • [x] Version 7.1 content
  • [x] Version 7.0 content
  • [x] Version 5.1 content

PR Checklist

  • [x] I have read the contributors guide and followed the style and process guidelines
  • [x] PR has a meaningful title
  • [x] PR is targeted at the staging branch
  • [x] All relevant versions updated
  • [x] Includes content related to issues and PRs - see Closing issues using keywords.
  • [ ] This PR is ready to merge and is not Work in Progress
    • If the PR is work in progress, please add the prefix WIP: or [WIP] to the beginning of the title and remove the prefix when the PR is ready.
+90 -16

0 comment

4 changed files

pr created time in 4 days

push eventchasewilson/PowerShell-Docs

chasewilson

commit sha 7c518577d78dcde83a47eb93c0d9b2b546c6e9eb

Automatically committed changes.

view details

push time in 4 days

create barnchchasewilson/PowerShell-Docs

branch : chasewilson-paramset

created branch time in 4 days

push eventchasewilson/PowerShell-Docs

Sean Wheeler

commit sha fc0a184b1880489b74589953071b2ef4efb59fee

Fixes #2884 - Remove empty article (#8103) * Remove empty article * Fix broken links

view details

Sean Wheeler

commit sha 044bfedc9f60b9a041d50eb4f24d10c55d898e68

Add note about platform compatibility (#8104)

view details

Sean Wheeler

commit sha f6d5658a690c8a9c0e9195bf410e4cba7159c7c0

Cleanup metadata frontmatter (#8105)

view details

Sean Wheeler

commit sha c1e5ad3000b848a31ba11a28a4dc5160af520b8e

Fix damaged file (#8107)

view details

Chase

commit sha 8e4cff531c3d10715a7e03a36443ff51238651de

minor typo correction

view details

Zhu-Panda

commit sha 8ad889b1486786dc6e9a62ef6cda6e3a8a8e947b

Fixed typo

view details

Sean Wheeler

commit sha fca650857fb6c8f3261aca702d0716411da8cfe7

Merge pull request #8109 from CHDAFNI-MSFT/patch-1 minor typo correction

view details

Sean Wheeler

commit sha 4307a2ad597065c18d82143843b00d029562d3d7

Merge pull request #8110 from Zhu-Panda/patch-1 Fixed typo

view details

Sean Wheeler

commit sha d77fda4fd2d14fca1fc43fd1bcfc37000779cc5f

Fix Example 3 (#8113)

view details

push time in 4 days

push eventMicrosoftDocs/PowerShell-Docs

Sean Wheeler

commit sha d77fda4fd2d14fca1fc43fd1bcfc37000779cc5f

Fix Example 3 (#8113)

view details

push time in 4 days

PR merged MicrosoftDocs/PowerShell-Docs

Fixes #8112 - Fix Example 3

PR Summary

<!-- Summarize your changes and list related issues here -->

Fixes AB#1878428 - Fixes #8112 - Fix Example 3

<!-- There is a numbered folder for each version of the PowerShell cmdlet content. Changes to cmdlet reference should be made to all versions where applicable. The /docs-conceptual folder tree does not have version folders. -->

Select the area of the Table of Contents containing the documents being changed.

Conceptual content

  • [ ] Overview and Install
  • [ ] Learning PowerShell
    • [ ] PowerShell 101
    • [ ] Deep dives
    • [ ] Sample scripts
    • [ ] Remoting
  • [ ] Release notes (What's New)
  • [ ] Windows PowerShell
    • WMF, ISE, release notes, etc.
  • [ ] DSC articles
  • [ ] Community resources
  • [ ] Gallery articles
  • [ ] Scripting and development
    • [ ] Language Spec
    • [ ] Legacy SDK

Cmdlet reference & about_ topics

  • [x] Preview content
  • [x] Version 7.1 content
  • [x] Version 7.0 content
  • [x] Version 5.1 content

PR Checklist

  • [x] I have read the contributors guide and followed the style and process guidelines
  • [x] PR has a meaningful title
  • [x] PR is targeted at the staging branch
  • [x] All relevant versions updated
  • [x] Includes content related to issues and PRs - see Closing issues using keywords.
  • [x] This PR is ready to merge and is not Work in Progress
    • If the PR is work in progress, please add the prefix WIP: or [WIP] to the beginning of the title and remove the prefix when the PR is ready.
+8 -8

1 comment

4 changed files

sdwheeler

pr closed time in 4 days

issue closedMicrosoftDocs/PowerShell-Docs

Bug in code for Example 3

I believe Example 3 contains an error in the following code segment:

Start-Process @$processOptions

The correct code should omit the dollar, and should be:

Start-Process @processOptions


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 4 days

JPruns
PullRequestReviewEvent

create barnchchasewilson/PowerShell-Docs

branch : chasewilson-ghi2882

created branch time in 7 days

push eventchasewilson/PowerShell-Docs

Sean Wheeler

commit sha 0e2f82f3cbf3beab290cf481817fbe76f08ef68d

Fixes #4079 - Add docs for ValidateScript (#8096) * Add docs for ValidateScript * Fix title * update TOC Co-authored-by: Chase Wilson <31453523+chasewilson@users.noreply.github.com>

view details

Sean Wheeler

commit sha 3316dfae2a6d8b2ea739494a72692ef0a719312f

Fix typo in example (#8102)

view details

Chase Wilson

commit sha 0370350bc31d2cefc890c7192ffaa5f9996b48c8

Fixes #4691 - Updates + 10 more (#8099) * Removes Modifying psmodule path * Adds redirect * Automatically committed changes. * Apply suggestions from code review Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com> * Automatically committed changes. * reflow Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com>

view details

push time in 7 days

push eventchasewilson/PowerShell-Docs

Chase Wilson

commit sha d88726640a5c958785920a46860369bdcc678fb4

Apply suggestions from code review Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com>

view details

chasewilson

commit sha 196484b9a79b0cc807a2946c6d9f0453230c9bf0

Merge branch 'chasewilson-ghi4691' of https://github.com/chasewilson/PowerShell-Docs into chasewilson-ghi4691

view details

push time in 7 days

push eventchasewilson/PowerShell-Docs

Chase Wilson

commit sha 87afe63708c5a3348f0d16e2cce54a27e7d57b42

Apply suggestions from code review Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com>

view details

push time in 7 days