Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Releases: PowerShell/vscode-powershell

v2022.11.2-preview

29 Nov 21:38
Compare
Choose a tag to compare
v2022.11.2-preview Pre-release
Pre-release

v2022.11.2-preview

Tuesday, November 29, 2022

vscode-powershell

Just dependency updates.

PowerShellEditorServices v3.6.3

v2022.11.1-preview

21 Nov 23:26
Compare
Choose a tag to compare
v2022.11.1-preview Pre-release
Pre-release

v2022.11.1-preview

Monday, November 21, 2022

vscode-powershell

PowerShellEditorServices v3.6.2

v2022.11.0

16 Nov 20:15
Compare
Choose a tag to compare

v2022.11.0

Wednesday, November 16, 2022

The November release represents a renewed focus on the client, that is, the TypeScript
extension for Visual Studio Code. We've paid back a significant amount of technical debt
by enabling both the TypeScript compiler's and ESLint linter's strict checks, helping us
ensure we are writing correct code. We've increased the client's logging, made the
walkthrough's installation instructions cross-platform, added a warning popup when custom
configured additional PowerShell executables aren't found, and fixed a couple debugger
configuration edge cases.

A regression for the OnIdle handler was fixed in the server, complete with regression
tests covering the registration and triggering of idle events registered both in a profile
and during a session. A workaround was implemented for a completion bug in PowerShell that
was causing the LSP session to disconnect when used with third-party clients. When
executing scripts, the path is now escaped with single quotes instead of double quotes,
addressing the edge case where a path contains a dollar sign, and is now inline with
PowerShell's semantics.

The build is now correctly published in release mode which should be more performant and
won't allow the user to accidentally enable the "wait for debugger" scenario (which can
appear as a hang, though it is a correctly working feature that is now hidden behind more
developer settings). Additionally, checks were added to both the server and client build
pipelines to assert that the bits are in release mode before packaging, as it was
unfortunately the act of running the tests that erroneously and silently overwrote release
bits with debug bits.

Finally, a long-standing bug that often prevented the server from starting with Windows
PowerShell was resolved. Known to users as the DryIoc error (which was a misleading
stacktrace that commonly popped up), we tracked down a broken dependency of OmniSharp that
when present and loaded into the GAC caused a type resolution error. While it took a year
for us to find the root cause, the fix was a single line dependency update for OmniSharp,
and then some work to incorporate the OmniSharp update into the server.

vscode-powershell

PowerShellEditorServices v3.6.1

v2022.11.0-preview

09 Nov 00:18
Compare
Choose a tag to compare
v2022.11.0-preview Pre-release
Pre-release

v2022.11.0-preview

Thursday, November 03, 2022

vscode-powershell

PowerShellEditorServices v3.6.1

v2022.10.2-preview

25 Oct 20:44
Compare
Choose a tag to compare
v2022.10.2-preview Pre-release
Pre-release

v2022.10.2-preview

Tuesday, October 25, 2022

vscode-powershell

PowerShellEditorServices v3.6.0

v2022.10.0

20 Oct 18:49
Compare
Choose a tag to compare

v2022.10.0

Thursday, October 20, 2022

This October stable release incorporates a number of bugfixes throughout September and
early October, though is not based on the latest preview, v2022.10.1-preview, as the
refactors involved in enabling TypeScript's strict type checking and ESLint's strict
linting will need more testing. However, based on the success of the PowerShell Script
Analyzer's v1.21.0 release we wanted to get this to you sooner!

Highlighted bugfixes include: supporting events registered to PowerShell's OnIdle
handler so that Azure cmdlets such as Az.Tools.Predictor now work, a lock around the
client's start() so the extension terminal cannot accidentally be spawned multiple
times, and making the default debug configurations not override your current working
directory (by unsetting cwd on all of them).

In addition to fixing bugs, we also reintroduced a fan-favorite feature: the PowerShell
Language Status Icon will visually indicate if the execution pipeline is busy. For
example, a long-running task in the PowerShell Extension Terminal or a launched editor
command will show a spinner!

Finally, I wanted to call out work by Patrick to significantly improve the performance of
reference finding (which powers the reference code lenses), so large workspaces can now be
used more easily. If these performance improvements are still not enough for a particular
workspace, we also introduced two new settings to fine-tune the feature:

  • powershell.analyzeOpenDocumentsOnly when enabled will only search for references within open documents
  • powershell.enableReferencesCodeLens can be used to disable reference finding without having to turn off other code lenses

vscode-powershell

PowerShellEditorServices v3.5.4

v2022.10.1-preview

18 Oct 01:59
Compare
Choose a tag to compare
v2022.10.1-preview Pre-release
Pre-release

v2022.10.1-preview

Monday, October 17, 2022

vscode-powershell

PowerShellEditorServices v3.5.4

No changes.

v2022.10.0-preview

08 Oct 02:25
Compare
Choose a tag to compare
v2022.10.0-preview Pre-release
Pre-release

v2022.10.0-preview

Friday, October 07, 2022

vscode-powershell

PowerShellEditorServices v3.5.4

No changes.

v2022.9.2-preview

30 Sep 21:50
Compare
Choose a tag to compare
v2022.9.2-preview Pre-release
Pre-release

v2022.9.2-preview

Friday, September 30, 2022

vscode-powershell

PowerShellEditorServices v3.5.4

v2022.9.1-preview

29 Sep 16:10
Compare
Choose a tag to compare
v2022.9.1-preview Pre-release
Pre-release

v2022.9.1-preview

Wednesday, September 28, 2022

vscode-powershell

PowerShellEditorServices v3.5.3