PowerShell Extension for Visible Studio Code October 2022 Replace

We’re excited to announce that the October replace to the PowerShell Extension for Visible Studio Code
is now obtainable on the extension market.

This October steady launch incorporates quite a lot of bugfixes all through September and
early October, although shouldn’t be primarily based on the most recent preview, v2022.10.1-preview, because the
refactors concerned in enabling TypeScript’s strict kind checking and ESLint’s strict
linting will want extra testing. Nevertheless, primarily based on the success of the PowerShell Script
Analyzer’s v1.21.0 launch we needed to get this to you sooner!

Updates within the October Launch

Be aware that these updates all shipped in our PowerShell Preview Extension
for VS Code earlier than transport in our steady channel.

Some highlights of the September and October preview releases:

For the complete checklist of modifications please check with our changelog.

Highlighted Bugfixes

Some main bugfixes we want to name out embrace:

• supporting occasions registered to PowerShell’s OnIdle handler in order that Azure cmdlets such
  as Az.Instruments.Predictor now work
• a lock across the consumer’s begin() so the extension terminal can not by chance be
  spawned a number of occasions
• making the default debug configurations not override your present working listing
  (by unsetting cwd on all of them).

Execution Busy Spinner

Along with fixing bugs, we additionally reintroduced a fan-favorite function: the PowerShell
Language Standing Icon will visually point out if the execution pipeline is busy. For
instance, a long-running activity within the PowerShell Extension Terminal or a launched editor
command will present a spinner!

References Efficiency Enhancements

Lastly, I needed to name out work by Patrick to considerably enhance the efficiency of
reference discovering (which powers the reference code lenses), so giant workspaces can now be
used extra simply. If these efficiency enhancements are nonetheless not sufficient for a specific
workspace, we additionally launched two new settings to fine-tune the function:

• powershell.analyzeOpenDocumentsOnly when enabled will solely seek for references inside open paperwork
• powershell.enableReferencesCodeLens can be utilized to disable reference discovering with out having to show off different code lenses

Getting Help and Giving Suggestions

Whereas we hope the brand new implementation supplies a a lot better person expertise, there are sure to be points. Please tell us in the event you run into something.

Should you encounter any points with the PowerShell Extension in Visible Studio Code or have function requests, the very best place to get help is thru our GitHub repository.

Andy Jordan,

PowerShell Workforce