[ad_1]
Three years after the release of PowerShell Core for Linux and macOS, Microsoft announced the launch of PowerShell 7, the latest version of PowerShell Core.
It was not until March that Microsoft released PowerShell Core 6.2, but instead of calling this version PowerShell Core 6.3, it was named version 7.
At the same time, Microsoft plans to release a "full replacement" of Windows PowerShell 5.1, the latest version of PowerShell for Windows only, released in 2016 and running on the .NET Framework unlike PowerShell Core, which runs on .NET. Heart.
As Microsoft explains on its developer blog, the adoption of PowerShell Core comes mostly from Linux users, suggesting that Microsoft had the right to extend the availability to non-Windows platforms .
The use of PowerShell by Linux is the main reason why the Microsoft programming language reached 45 for the first time in March in the popularity index of the Tiobe programming language.
However, the use of PowerShell Core by Windows has remained unchanged, representing today less than 20% of the approximately 11 million PowerShell startups.
"We think this could happen because existing Windows PowerShell users have automation that is incompatible with PowerShell Core, due to unsupported modules, assemblies, and APIs," explains Steve Lee, Senior PowerShell Software Engineer.
"These people are unable to take advantage of PowerShell Core's new features, increased performance, and bug fixes."
The Microsoft chart shows the number of times that pwsh.exe, or only pwsh on Linux / macOS, was started unless telemetry was disabled.
Image: Microsoft
To boost the use of Windows, Microsoft plans to release a "complete replacement of Windows PowerShell 5.1" so that Windows PowerShell and PowerShell Core users on other platforms have the same version of PowerShell.
In addition, PowerShell 7 users will have a "very high level of compatibility" with the Windows PowerShell modules used today.
"PowerShell Core 6.1 has provided compatibility with many built-in Windows PowerShell modules, and we believe that PowerShell 7 can achieve compatibility with more than 90 percent of the Windows PowerShell modules in the inbox by taking advantage of changes to .NET Core 3.0 modules built on the .NET Framework, so they work with the .NET Core runtime, "explained Lee.
Microsoft plans to remove the "Core" in its documentation for PowerShell 7 and align it with the .NET Core support lifecycle, which will enable a LTS (Long Term Service) version and a non-LTS version.
Users should be able to access the first preview version of PowerShell 7 in May, but the actual date depends on the progress of Microsoft's work on the integration of PowerShell to .NET Core 3.0. Microsoft expects it to reach general availability (GA) sometime after .NET Core 3.0 has reached GA.
PowerShell 7 will eventually ship with Windows alongside Windows PowerShell 5.1, but as the .NET Core timeline does not match Windows updates, it is unclear with which version of Windows 10 and Windows Server it will be delivered.
More information about Microsoft PowerShell
[ad_2]
Source link