

PowerShell Extension for Visual Studio Code July 2022 Update
source link: https://devblogs.microsoft.com/powershell/powershell-extension-for-visual-studio-code-july-2022-update/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

PowerShell Extension for Visual Studio Code July 2022 Update

Steve Lee

Sydney Smith
July 31st, 20220
We are excited to announce that the July update to the PowerShell Extension for Visual Studio Code
is now available on the extension marketplace.
This release renames the “PowerShell Integrated Console” to the “PowerShell Extension Terminal” to align with VS Code’s verbiage, adds many regression tests, and includes a number of bug fixes!
Updates in the July release
Note that these updates all shipped in our PowerShell Preview Extension for VS Code before shipping in our stable channel.
Some highlights of July release:
- vscode-powershell #4093 – Use
globalStorageUri
for log and session files.- vscode-powershell #4053 – Rename “Integrated Console” to “Extension Terminal”.
- PowerShellEditorServices #1849 – Add
Directory.Exists()
check toSetInitialWorkingDirectoryAsync()
.
For the full list of changes please refer to our changelog.
Improvements to our tests
We are currently building out regression tests for the extension to cover everything we broke and subsequently fixed during the major rewrite earlier this year. We have a strong focus on quality, and want to ensure we continue to deliver a production-ready, high-quality extension to you, our users. We have made a large investment in improving the extension so we want to be able to confidently continue to iterate on this project without inadvertently impacting the performance, stability, or feature set.
We’ve begun this work already, and are tracking in our GitHub repository.
Some highlights of this work so far include:
- PowerShellEditorServices #1846 – Add end-to-end Pester unit test.
- PowerShellEditorServices #1857 – Add regression test for
$PSDebugContext
inprompt
function. - PowerShellEditorServices #1858 – Add regression test for debugging script with dot-source operator.
- PowerShellEditorServices #1861 – Add
DebuggerBreaksInUntitledScript
unit test. - PowerShellEditorServices #1859 – Update and extend CI matrix.
- PowerShellEditorServices #1793 – Improve CI stability.
Getting support and giving feedback
While we hope the new implementation provides a much better user experience, there are bound to be issues. Please let us know if you run into anything.
If you encounter any issues with the PowerShell Extension in Visual Studio Code or have feature requests, the best place to get support is through our GitHub repository.
Sydney PowerShell Team
Steve Lee Principal Software Engineer Manager, PowerShell
Follow
Sydney Smith PM, PowerShell
Follow
Recommend
-
8
We are excited to announce that an update to our PowerShell extension is now available on the Visual Studio Code Marketplace. This blog will...
-
9
Major update to the PowerShell Extension for Visual Studio Code Sydney S May 3rd, 2022
-
7
PowerShell Extension for Visual Studio Code June 2022 Update Sydney...
-
7
Java on Visual Studio Code Update – July 2022 Nick Zhu...
-
8
PowerShell Extension for Visual Studio Code August 2022 Update Sydne...
-
8
PowerShell Extension for Visual Studio Code October 2022 Update
-
6
PowerShell Extension for Visual Studio Code January 2023 Update Sydn...
-
3
PowerShell Extension for Visual Studio Code February 2023 Update Syd...
-
9
PowerShell Extension for Visual Studio Code Spring 2023 Update
-
4
PowerShell Extension for Visual Studio Code Fall 2023 Update Sydney...
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK