Windows PowerShell and PowerShell 7 compatibility

This page's changes and edits · All guidance changes

Microsoft's edit · 8 Apr 20:58 UTC

(AB-568561) `[switch]` parameter in conceptual docs (#12939)

Microsoft's commit message in MicrosoftDocs/PowerShell-Docs · commit 46dd905 · +4 −4 lines · also on GitHub

⋯ 317 unchanged lines

318318

319319 ## Improved backwards compatibility with Windows PowerShell

320320

321 −For Windows, a new switch parameter **UseWindowsPowerShell** is added to `Import-Module`. This

322 −switch creates a proxy module in PowerShell 7 that uses a local Windows PowerShell process to

321 +For Windows, a new `[switch]` parameter **UseWindowsPowerShell** is added to `Import-Module`. This

322 +parameter creates a proxy module in PowerShell 7 that uses a local Windows PowerShell process to

323323 implicitly run any cmdlets contained in that module. For more information, see [Import-Module][14].

324324

325325 For more information on which Microsoft modules work with PowerShell 7.0, see the

⋯ 492 unchanged lines

818818 `PSModulePath` environment variable. However, it only exposes modules to `Get-Module` and

819819 `Import-Module` if its `CompatiblePSEdition` is marked as compatible with `Core`.

820820

821 −You can override this behavior to show all modules using the `-SkipEditionCheck` switch parameter.

822 −We've also added a `PSEdition` property to the table output.

821 +You can override this behavior to show all modules using the `-SkipEditionCheck` `[switch]`

822 +parameter. We've also added a `PSEdition` property to the table output.

823823

824824 ### `-lp` alias for all `-LiteralPath` parameters

825825

⋯ 428 unchanged lines

Microsoft's Markdown source from MicrosoftDocs/PowerShell-Docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 03:16 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.