After 6 previews, we’re happy to announce the release of the PowerShell 7 Release Candidate (RC). Whether you’ve been running PowerShell Core since our first alpha releases or you’ve been clinging to Windows PowerShell for backwards compatibility, 7.0 delivers a host of improvements to make your life better.
Post by this author
Beginning with Windows Server 20H1 Insider builds, Windows Server Core Insider images have been reduced in size from ~2.1 GBs to ~1.1 GBs.
How did the Server Core images get over 40% smaller?
Traditionally, Windows 10 and Windows Server have always included a set of .NET native binaries that were pre-compiled using the Native Image Generator tool (Ngen.exe).
Over the last six months, we’ve been hard at work integrating PowerShell Core with Azure Functions 2.x. Today, I’m happy to announce that we’re releasing public preview of PowerShell support for Azure Functions 2.x for Windows (Consumption, Premium, and App Service pricing plans).
The goal of PowerShell Core is to be the ubiquitous language for managing your assets in the hybrid cloud. That’s why we’ve worked to make it available on many operating systems, architectures, and flavors of Linux, macOS, and Windows as possible.
PowerShell Core 6.0 is a new edition of PowerShell that is cross-platform (Windows, macOS, and Linux), open-source, and built for heterogeneous environments and the hybrid cloud.
First and foremost, thank you to all of our amazing community, especially our open-source contributors (the most recent of which you can find on our community dashboard at https://aka.ms/PSGitHubBI) for donating your time and energy to PowerShell Core.
I’m thrilled to share that a Beta OpenSSH client and server daemon are available as a Feature-on-Demand in Windows 10 Fall Creators Update and Windows Server 1709. Since our last update blog, we’ve been working hard on a Win32 port of OpenSSH and working closely with members of the OpenSSH Portable and OpenBSD projects with the eventual goal of bringing Win32 support upstream into OpenSSH Portable.
We recently announced that Windows PowerShell 2.0 is being deprecated in the Windows 10 Fall Creators Update. Deprecation is a process whereby technologies or applications are marked as legacy, signalling to users that they may be removed in the future, and that should move away from them and towards newer alternatives.
As we’ve made progress on open-source PowerShell, it’s time to start talking more in-depth about:
different editions of PowerShell
PowerShell’s relationship to .NET Core and .NET Standard
the future of PowerShell
when you might expect to start taking a dependency on PowerShell Core 6.0 in production
There are two editions of PowerShell:
Windows PowerShell is the edition of PowerShell built on top of .NET Framework
(sometimes referred to colloquially as “FullCLR”):
This is the PowerShell that has been in widespread use for the last ~10 years.
tl;dr: PowerShell Core Community Calls are on the third Thursday of every month at 9:30am Pacific Time (note, this is currently PDT). Use this .ics file (right-click and select Save Target/Link As in order to download the file correctly) to avoid missing one.