Over the last year we have committed to making the PowerShell editing experience in Visual Studio Code a rich and productive cross-platform alternative for the PowerShell ISE. To that end, we have focused on two primary areas: bringing the PSReadLine experience to the Integrated Console,
Post by this author
Beginning in PowerShell 7 Preview 3, PowerShell will be sending some additional data points to Microsoft.
This data will allow us to better understand usage of PowerShell and enable us to prioritize our future investments.
These additional points of data were reviewed with the PowerShell community and approved by the PowerShell Committee through the PowerShell RFC process.
We have improved the experience with PowerShellGet and private NuGet feeds by focusing on pain points using an Azure Artifacts feed.
We addressed pain points by enabling/documenting the following features:
Non-PAT authentication for package management
Credential persistence in Register-PSRepository
These improvements will effect the following cmdlets:
What is Azure Artifacts and Why would I use it?
Over the past few months, the team has been working hard to make the PowerShell Gallery as accessible as possible. This blog details why it matters and what work has been done.
Why making the PowerShell Gallery more accessible was a priority
Accessible products change lives and allow everyone to be included in our product.
Commenting on the PowerShell Gallery is provided by LiveFyre–a third-party comment system. LiveFyre is no longer supported by Adobe and therefore we are unable to service issues as they arise. We have gotten reports of authentication failing for Twitter and Microsoft AAD and unfortunately we are unable to bring back those services.
We are excited to announce the PowerShell Extension is available in the Azure Data Studio (ADS)
Now you can write PowerShell scripts with the full benefits of PowerShell Editor Services
using the excellent IDE-like interface that Azure Data Studio provides.