The PowerShell team has introduced a new preview version of PowerShell. Here is what to expect in the upcoming PowerShell 7.1 platform, and what has already changed in Preview 7.
The preview release of PowerShell 7.1 includes .NET 5 preview 1. Starting with PowerShell 7.0, devs have shifted to align with .NET’s release and support life-cycle more closely. PowerShell 7.1 is expected to become available within a week or two of .NET 5’s release date of winter 2020 and align with their annual release cadence going forward.
Starting with Preview 6, PowerShell 7.1 Preview is available in Microsoft Store.
What's new in PowerShell 7.1 Preview 6
$?to not be
$falsewhen native command writes to
Engine Updates and Fixes
- Initial work of the subsystem plugin model (for minimal powershell) (#13186)
GetSystemLockdownPolicyfor non-lockdown scenarios (#13438)
General Cmdlet Updates and Fixes
- Revert "Add the parameter
Get-Helpto support paging (#13374)" (#13519)
- Add support for
TLS1.3 in Web cmdlets (#13409) (Thanks @iSazonov!)
- Add null check for
CommandLineParser(#13451) (Thanks @iSazonov!)
- Process reparse points for Microsoft Store applications (#13481) (Thanks @iSazonov!)
PSNullConditionalOperatorsfeature out of experimental (#13529)
PSNativePSPathResolutionfeature out of Experimental (#13522)
- Use field if property does not exist for
ObRootwhen using PowerShell Direct to container (#13375) (Thanks @hemisphera!)
UTF-7obsolete warnings (#13484)
- Avoid multiple enumerations of an
Add-Type -OutputTypeto not support
- Create warnings when
UTF-7is specified as an encoding (#13430)
- vscode: Add
editorconfigto recommended extensions (#13537) (Thanks @xtqqczze!)
- Remove the out-dated
ZapDisablerelated code from
build.psm1(#13350) (Thanks @jackerr3!)
WMFdownload link validation test (#13479)
What to expect in PowerShell 7.1
- PowerShellGet 3.0
- Secret Management Module, an extensible abstraction layer in PowerShell for interacting with Secrets and Secrets Vaults, will get Linux support.
- PSScriptAnalyzer 2.0 for better user experience with VSCode-PowerShell and PSEditorServices.
- Improvements made to PowerShell Jupyter Kernel
- Improvements made to platyPS vNext, a PowerShell module that devs currently use to convert PowerShell documentation from markdown to updatable-help.
There are also a number of areas where it is possible to make more improvements and changes, including Installation and Updating, Shell Improvements, Interactive User Experience.
Finally, PowerShell may get a minimal setup, that only includes the parts of PowerShell needed for your scripts. Not only would it take less disk space, but more importantly, a minimal set of code means less patching and security attack surface.
You can download it here:
Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:
If you like this article, please share it using the buttons below. It won't take a lot from you, but it will help us grow. Thanks for your support!