These improvements are described in detail in the vscode-powershell changelog for its 0.9.0 release.
- Added PowerShell code formatting integration with PSScriptAnalyzer
- Improved PSScriptAnalyzer execution, now runs asynchronously
- Added Document symbol support for .psd1 files
- Remote session and debugging support via Enter-PSSession (PowerShell v4+)
- "Attach to process/runspace" debugging support via Enter-PSHostProcess and Debug-Runspace (PowerShell v5+)
- Initial
pseditcommand support for loading files from remote sessions - Added language server protocol request for gathering PowerShell host processes for debugging
- Many minor improvements to the debugging experience
- Added
FileContext.Close()method to close an open file
- Fixed #339: Prompt functions that return something other than string cause the debugger to crash
- Added support for "suggested corrections" from PSScriptAnalyzer
- Added support for getting and setting the active list of PSScriptAnalyzer rules in the editing session
- Enabled the user of PSScriptAnalyzer in the language service on PowerShell versions 3 and 4
- Added PSHostUserInterface support for IHostUISupportsMultipleChoiceSelection
- Added $psEditor.Workspace
- Added $psEditor.Window.Show[Error, Warning, Information]Message methods for showing messages in the editor UI
- Added $psEditor.Workspace.Path to provide access to the workspace path
- Added $psEditor.Workspace.GetRelativePath to resolve an absolute path to a workspace-relative path
- Added FileContext.WorkspacePath to get the workspace-relative path of the file
- Enabled setting variable values from the debug adapter protocol
- Added breakpoint hit count support invthe debug service
- Added a new TemplateService for integration with Plaster
- Refactored PSScriptAnalyzer integration to not take direct dependency on the .NET assembly
- Fixed #138: Debugger output was not being written for short scripts
- Fixed #242: Remove timeout for PSHostUserInterface prompts
- Fixed #237: Set session's current directory to the workspace path
- Fixed #312: File preview Uris crash the language server
- Fixed #291: Dot-source reference detection should ignore ScriptBlocks
- Fixed #284: PowerShellContext.AbortException crashes when called more than once
- Fixed #285: PSScriptAnalyzer settings are not being passed to Invoke-ScriptAnalyzer
- Fixed #287: Language service crashes when invalid path chars are used in dot-sourced script reference
- Fixed PowerShell/vscode-powershell#246: Restore default PSScriptAnalyzer ruleset
- Fixed PowerShell/vscode-powershell#248: Extension fails to load on Windows 7 with PowerShell v3
This release marks the beginning of our support for Linux and macOS via the new cross-platform release of PowerShell.
NuGet packages will be provided in the upcoming 0.7.1 release.
- Introduced a new TCP channel to provide a commonly-available communication channel across multiple editors and platforms
- PowerShell Script Analyzer integration has been shifted from direct use via DLL to consuming the PowerShell module and cmdlets
- Updated code to account for platform differences across Windows and Linux/macOS
- Improved stability of the language service when being used in Sublime Text
- Fixed #264: Variable and parameter IntelliSense broken in VS Code 1.4.0
- Fixed #240: Completion item with regex metachars can cause editor host to crash
- Fixed #232: Language server sometimes crashes then $ErrorActionPreference = "Stop"
- Fixed #221: Language server sometimes fails to initialize preventing IntelliSense, etc from working
- Fixed #222: Editor commands are not receiving $host.UI prompt results
- We have launched a new documentation site for this project on GitHub Pages. This documentation provides both a user guide and .NET API documentation pages that are generated directly from our code documentation. Check it out and let us know what you think!
- We've added a new extensibility model which allows you to write PowerShell
code to add new functionality to Visual Studio Code and other editors with
a single API. If you've used
$psISEin the PowerShell ISE, you'll feel right at home with$psEditor. Check out the documentation for more details!
- We've now introduced the
$profilevariable which contains the expected properties that you normally see inpowershell.exeandpowershell_ise.exe:AllUsersAllHostsAllUsersCurrentHostCurrentUserAllHostsCurrentUserCurrentHost
- Each editor integration can specify what their host-specific profile filename
should be. If no profile name has been specified a default of
PowerShellEditorServices_profile.ps1is used. - Profiles are not loaded by default when PowerShell Editor Services is used. This behavior may change in the future based on user feedback.
- Editor integrations can also specify their name and version for the
$host.Nameand$host.Versionproperties so that script authors have a better idea of where their code is being used.
$envvariables now have IntelliSense complete correctly (#206).- The debug adapter now does not crash when you attempt to add breakpoints for files that have been moved or don't exist (#195).
- Fixed an issue preventing output from being written in the debugger if you don't set a breakpoint before running a script.
- Debug adapter now doesn't crash when rendering an object for the variables view if ToString throws an exception.
- Support for PowerShell v3 and v4 is now complete! Note that for this release, Script Analyzer support has been disabled for PS v3 and v4 until we implement a better strategy for integrating it as a module dependency
- Added support for command breakpoints
- Added support for conditional breakpoints
- Improved the debug adapter startup sequence to handle new VS Code debugging features
using 'module'now resolves relative paths correctly, removing a syntax error that previously appeared when relative paths were used- Calling
Read-Host -AsSecureStringorGet-Credentialfrom the console now shows an appropriate "not supported" error message instead of crashing the language service. Support for these commands will be added in a later release.
- Fixed #166: PowerShell Editor Services should be usable without PSScriptAnalyzer binaries
- Fixed #127: Update to PSScriptAnalyzer 1.4.0
- Fixed #149: Scripts fail to launch in the debugger if working directory path contains spaces
- Fixed #153: Script Analyzer integration is not working in 0.4.1 release
- Fixed #159: LanguageServer.Shutdown method hangs while waiting for remaining buffered output to flush
- Fixed #147: Running native console apps causes their stdout to be written in the Host
- A new
Microsoft.PowerShell.EditorServices.Host.x86.exeexecutable has been added to enable 32-bit PowerShell sessions on 64-bit machines (thanks @adamdriscoll!) - You can now pass arguments to scripts in the debugger with the
LaunchRequest.Argsparameter (thanks @rkeithhill!) - You can also set the working directory where the script is run by setting the
LaunchRequest.Cwdparameter to an absolute path (thanks @rkeithhill!)
-
Improved PowerShell console output formatting and performance
- The console prompt is now displayed after a command is executed
- Command execution errors are now displayed correctly in more cases
- Console output now wraps at 120 characters instead of 80 characters
- Console output is now buffered to reduce the number of OutputEvent messages sent from the host to the editor
-
Added choice and input prompt support. Prompts can be shown either through the console or natively in the editor via the
powerShell/showInputPromptandpowerShell/showChoicePromptrequests.
/logLevel:<level>: Sets the log output level for the host. Possible values:Verbose,Normal,Warning, orError./logPath:<path>: Sets the output path for logs written while the host is running
- Initial work has been done to ensure support for PowerShell v3 and v4 APIs by compiling against the PowerShell reference assemblies that are published on NuGet. (thanks @adamdriscoll!)
- Initial WebSocket channel support (thanks @adamdriscoll!)
- Removed Nito.AsyncEx dependency
- Fixed issue PowerShell/vscode-powershell#49, Debug Console does not receive script output
- First release with official NuGet packages!
- Microsoft.PowerShell.EditorServices - Core .NET library
- Microsoft.PowerShell.EditorServices.Protocol - Protocol and client/server library
- Microsoft.PowerShell.EditorServices.Host - API host process package
- Introduced a new client/server API in the Protocol project which makes it much easier to write a client or server for the language and debugging services
- Introduced a new channel model which makes it much easier to add and consume new protocol channel implementations
- Major improvements in variables retrieved from the debugging service:
- Global and script scope variables are now accessible
- New "Autos" scope which shows only the variables defined within the current scope
- Greatly improved representation of variable values, especially for dictionaries and objects that implement the ToString() method
- Added new "Expand Alias" command which resolves command aliases used in a file or selection and updates the source text with the resolved command names
- Reduced default Script Analyzer rules to a minimal list
- Improved startup/shutdown behavior and logging
- Fixed a wide array of completion text replacement bugs
- Added Online Help command
- Enabled PowerShell language features for untitled and in-memory (e.g. in Git diff viewer) PowerShell files
- Fixed high CPU usage when completing or hovering over an application path
Initial release with the following features:
- IntelliSense for cmdlets and more
- Rule-based analysis provided by PowerShell Script Analyzer
- Go to Definition of cmdlets and variables
- Find References of cmdlets and variables
- Document and workspace symbol discovery
- Local script debugging and basic interactive console support