People are currently reading this guide.
 |
| Image Credits: Microsoft Docs |
Last month, Microsoft announced an increase in use of PowerShell on all platforms.
The new update will directly affect PowerShell in version 7. In a blog post, Microsoft explained why the company decided to upgrade from version 6.2 to version 7. You can read the blog post here.
In other words, Microsoft wants to put all platforms in the same version of PowerShell for better cross-platform compatibility. Microsoft has also made changes to the life cycle of PowerShell support. The company will launch LTS (long-term service) and non-LTS version of PowerShell to align it with the life cycle of .NET Core support. Microsoft will release PowerShell 7 for Windows users, but it will allow users to switch between PowerShell 5.1 and PowerShell 7.
Microsoft has released the 7th PowerShell Preview. Microsoft plans to launch a new preview every month. The general availability of PowerShell will take time because Microsoft needs to synchronize the version with .NET Core 3.0.
What Microsoft said:
PowerShell Core usage has grown significantly in the last two years. In particular, the bulk of our growth has come from Linux usage, an encouraging statistic given our investment in making PowerShell viable cross-platform…Source: Microsoft Blog
However, we also can clearly see that our Windows usage has not been growing as significantly, surprising given that PowerShell was popularized on the Windows platform…
This means that Windows PowerShell and PowerShell Core users will be able to use the same version of PowerShell to automate across Windows, Linux, and macOS and on Windows, and PowerShell 7 users will have a very high level of compatibility with Windows PowerShell modules they rely on today.
 |
