September 21st 2023 PowerShell Community Call

[StevenBucher98]

Agenda (more to come)

• PS Adapters Release @StevenBucher98
• WinGet Feedback Provider @carlos-zamora @crutkas
• Experimental Features for 7.4 @SteveL-MSFT
• PSresourceGet rc release @anamnavi @SydneyhSmith @alerickson
• Docs update @sdwheeler
• VS Code pre-release(s) (and upcoming stable release) @SydneyhSmith
• DSC alpha.2 @mgreenegit @SteveL-MSFT
• PSReadLine GA - @StevenBucher98
• Gallery potential intermittent connection issues on Thursday (moving prod to Front Door) and stats update @SydneyhSmith
• Ignite @SydneyhSmith @StevenBucher98
• November End-of-Year Community Call (2nd Thursday of the month) @SteveL-MSFT
• December Community Call @SteveL-MSFT

[mgreenegit]

New PowerToy that adds the ability to detect failed commands in PowerShell and suggest a package to install using WinGet. This PowerToy is powered by a PowerShell module that leverages the new feedback subsystem.

Quick demo and feedback
microsoft/PowerToys#26319

[anamnavi]

Other agenda topics:

• PSresourceGet rc release
• Docs update
• VS Code pre-release(s) (and upcoming stable release)
• DSC alpha.2
• Gallery potential intermittent connection issues on Thursday (moving prod to Front Door) and stats update

[theJasonHelmick]

Can we please add

• November End-of-Year Community Call (2nd Thursday of the month) - Steve Lee
• December Community Call - Steve Lee

[StartAutomating]

If there's time, I can talk about:

• Pacific PowerShell User Group
• More on Posh
• PSA - A new module for Announcements and BlueSky
• This month HelpOut got a nice batch of changes that let us document ETS more effectively.
• There's also the useful module I use everyday, ugit

[AspenForester]

Just as a heads-up: I added info to Azure/azure-powershell#14416 this week. It seems to me that there's a reasonably clear path toward achieving simultaneous compatibility between ExchangeOnlineManagement and Azure PowerShell Modules like Az.Storage. There are similar issues with certain Microsoft.Graph and Az.* modules that I suspect may have a similar root cause. If anyone else has thoughts on this, please add them to issue 14416.

[dcaro]

Thanks, this looks like an assembly conflict. It is too late to address this for the release of next week, but we'll look at it for the next one.