Fixed an issue where Generate Proxy Function would run on empty command names and show an error in the terminal
PSScriptPad now persists loaded WPF assembly locations so they are loaded when the application is restarted
Added toolbox support for the WPF designer in PSScriptPad
Fixed an issue where PSScriptPad could crash when opening a XAML file
Fixed a licensing issue with a 3rd party component
Added support for the PSScriptPad WPF Designer
Fixed an issue where Generate Proxy Function would show errors in the terminal
Fixed an issue where non-subscription licenses would show they were only licensed for 1 week when this wasn't actually the case.
Added Generate Proxy Function refactoring
Fixed an issue with convert to $_ and convert to $PSItem refactorings
Added Enhanced Hover support
Fixed an issue where the Variable Explorer would cause a memory leak
Fixed issue with Split Pipeline refactoring changing the functionality of a script
Added integration into VS Code refactoring provider system
Added Convert to $PSItem refactoring
Added Convert to $_ refactoring
Fixed an issue where Split Pipeline would show on one-command pipelines
Reorganized tree view providers
Added Help and Information node
Fixed an issue where an error could be shown if the tree view was clicked before the extension was fully loaded
Added options for hiding tree view providers
Added an option to enable module update checks (now disabled by default) as it was slow on many machines
Added support for the PowerShell Preview extension
Added Reorder Parameters
Added Generate Function from Usage Refactoring
Added Convert To Multiline Command Refactoring
Fixed an issue where variables wouldn't work in PowerShell 7.1
Fixed an issue where Out-VSCodeGridView wouldn't work in PowerShell 7.1
Added a command to insert paths from Provider Explorer
Added a command to view child items of a path in Provider Explorer
Added a command to view item properties in Provider Explorer
Fixed an issue where ignored elements were case sensitive
Added support for expanding paths in strings
Added support for ignoring paths
Fixed an issue where RapidSense wouldn't refresh caches after changing settings
Added Ignored Variables setting to RapidSense
Fixed an issue where the PowerShell Pro Tools module wouldn't be imported correctly
Fixed an issue where the profiler failing to return results
Added millisecond timing to the profiler
Added support for PowerShell Pro Tools subscriptions
Changed purchasing links to point to new store
Fixed an issue where collections would not expand correctly.
Added support for scoped package.psd1 files
Fixed an issue where the packager could fail when packaging certain Windows PowerShell modules.
Fixed an issue where the PoshTools extension would fail to load if the user profile contained spaces.
Fixed an issue with packaging the NTFSSecurity module
Fixed an issue where the packager would state that there was unreachable code detected
Fixed an issue where the profile would run within the PoshTools host process rather than in the PowerShell process.
Fixed an issue where packaging would fail with a duplicate assembly error
Added support for Mac OS
Fixed an issue with bundling modules that contained System.Management.Automation.dll
Fixed an issue with bundling modules that contained RootModules nested in a folder
Fixed an issue in PSScriptPad where variables would not be shown during debugging.
Fixed an issue with bundling the ActiveDirectory module in PowerShell 7 standalone executables
Support for Linux
Fixed an issue with packaging Windows Forms applications with PS7
Added support for packaging the 7.0.2 and 7.0.3 PowerShell SDK
Default install of trial license
Added "Generate Tool" command
Updated to the latest version of PSScriptPad
Fixed an issue with Form Generation where it would generate forms with common parameters
PowerShell Pro Tools: Install PowerShell Pro Tools Module command
Fixed an issue that would cause the extension to delay on startup and occasionally time out
Fixed an issue with PSScriptPad where the variables window wouldn’t expand variables correctly
Fixed an issue that would cause a delay on start up
Fixed an issue where ListView, TreeView and ContextMenu child items would not work in PSScriptPad
VS Code extension now installs the PowerShell module automatically so it loads correctly
Fixed an issue where packaging would fail if a script ended in a comment
Fixed an issue where packaging would fail if a script was too large
Fixed an issue where the opacity setting wouldn’t work on form controls on certain systems.
Fixed an issue where the PowerShell Pro Tools host process could lock up
Fixed an issue where installing a license would report failure when it was actually succeeding.
Changed the license notification text and link as new licenses have been deployed to all affected customer’s accounts
Fixed an issue where launching more than one version of VS Code would cause the extension to fail to connect
Fixed an issue where the extension could fail to connect to the PowerShell process.
The provider tree view now runs within the main runspace.
Added Host Processes tree node with support for one-click debugging runspaces
Added an Output Channel for PowerShell Pro Tools diagnostics
PowerShell Pro Tools now uses an external process rather than being hosted directly in PowerShell
Fixed an issue where the PowerShell Pro Tools module would load over and over again
Fixed an issue where the variable window would not show variables
Fixed an issue with the form designer that wouldn’t be marked dirty when properties were edited
Fixed an issue with the form designer where it wouldn’t save StatusStrip items
Fixed an issue with the form designer where it wouldn’t change the main PS1’s form name if it was changed in the designer
Fixed an issue with the profiler where it would not work if params or using statements were used.
Added support for packaging PowerShell 7 executables
Added experimental support for packaging Linux and OSX executables
Fixed an issue with PSScriptPad that was causing hangs when running WinForm scripts.
Cmdlets for managing VS Code with PowerShell
Fixed an issue with the variables view showing incorrect child items
Improved the expansion of child items in the variables view
Improved the generation of child item paths
Fixed an issue where putting an apostrophe in a label would cause the Form Designer to fail to load
Fixed an issue where copy and pasting text into PSScriptPad would cause it to crash
Fixed an issue with the variable view not showing variables.
– Added a $Service object to OnStart\OnStop for packaged services to access the ServiceBase for the service – Added $ProcessArgs and $ServiceArgs variables to the runspace for packaged services
– Fixed an issue where $PSScriptRoot would not work for packaged services
– Fixed an issue where an error would be shown when loading the extension– Fixed an error where loading the module tree would cause the extension to become unresponsive
– Fixed an issue where a failed packaging build would not show the error message in the output
– Added -ProductId to New-Installer – Added -ScriptArguments to New-InstallerCustomAction – Added an option to add a context menu item for opening PS1 files with PSScriptPad – Added support for Comment (Ctrl+K,Ctrl+C) and Uncomment (Ctrl+K,Ctrl+U) keyboard shortcuts in PSScriptPad – Added support for reloading files updated outside of PSScriptPad
– Fixed issue with installer shortcuts throwing an exception if a workingDirectory or arguments were not specified – Fixed an issue where the installer shortcut working directory would not be specified correctly – Fixed an issue where the installer shortcut would not use the correct PowerShell variable – Fixed an issue where adding images to the installer UI on Windows PowerShell would throw an exception – Fixed an issue where PSScriptPad would crash on startup.
– Added support for WorkingDirectory on New-InstallerShortcut – Added support for Arguments on New-InstallerShortcut – Added support for Show on New-InstallerShortcut – Added support for Arguments on New-InstallerCustomAction
– Fixed issue where packaged applications wouldn’t work with arguments with spaces – Fixed issue with installer cmdlets not resolving paths correctly – When specifying a shortcut for an installer, if it’s a PS1, it will automatically launch PowerShell.exe rather than targeting the script
No longer requires a trial key
PowerShellProTools module is now signed
Fixed an issue with PSScriptPad that was preventing typing while IntelliSense was running in the terminal
Support for generating resources such as images and icons for WinForms.
Fixed issue with packaging resources used for WinForms.
Fixed an issue where licensing would attempt to activate more than once and sometimes failing which resulted in some users not being able to use the tools.
Fixed an issue where packaging config would not respect the platform property.
Fixed an issue where packaging would use a package.psd1 in the temp directory.
Fixed an issue where packaging would throw an invalid format exception
Fixed an issue with package architecture
Added support for setting the architecture of the exectuable that is created when packaging
Replaced Windows Form Designer with PSScriptPad
Fixed an issue with ToolStrip items.
Fixed an issue with deleting components
Added breakpoint support to the Windows Form Designer
Added stepping support to the Windows Form Designer
Added support for stopping debugger to the Windows Form Designer
Improved performance of IntelliSense
Fixed a bug where the Windows Form Designer would lose code-behind changes on startup.
The Windows Forms Designer can now execute PowerShell to show the form you are designing.
The Windows Forms Designer can now package the Windows Form as a executable
An output window was added to the Windows Forms Designer so you can see the output from your PS scripts.
Fixed an issue where the Actipro license was not installed correctly resulting in a popup.
The Windows Forms Designer properties and toolbox are now in a dockable tool window.
The Windows Forms Designer now supports moving controls with the arrow keys.
We’ve made it easier to open the Windows Form Designer from a PowerShell file. Just click the new Show Windows Form Designer button from your form.ps1 file.
In certain circumstances, when you would execute PowerShell Pro Tools commands, an E_PIPE error would be shown even though the command was completed successfully.