Microsoft last month announced the next version of PowerShell - PowerShell 7 of the relevant information, and explains why 6.2 from 7 to jump directly.
Just yesterday, Microsoft released PowerShell first preview version 7 , according to their update rhythm, every month it will launch a new preview version until the GA release. Preview version includes some changes have not been implemented in version 6.2, of course, more importantly, it means that PowerShell being migrated to the .NET Core 3.0.
As the announcement issued last month, in order to make consistent PowerShell life cycle of 7 and .NET Core, GA version will be re-launched after the .NET Core 3.0 release GA.
.NET Core 3.0
One of the biggest changes PowerShell 7 is a code library (from .NET 2.1) ported to .NET Core 3.0. Migrated to .NET Core 3.0 is not only a significant improvement in performance, but also brought many new API, including WPF and WinForms.
In the Windows platform compatibility
PowerShell 7 Although the version number directly from the transition from 6.2, but it still was asked to become a viable alternative to Windows PowerShell 5.1, allowing users to switch between PowerShell 5.1 and PowerShell 7. This means that the module is compatible with the respect that comes with Windows, it must almost be consistent with PowerShell.
More feedback feature request
- Improved error default format
- Ubiquitous -OnError {ScriptBlock} parameter
- Link control commands (chaining commands) operator
- Ternary conditions
- Air condition assignment
- Parallel For-Each-Object
Detailed instructions and download the updated address, please click here to view .