PowerShell Pro Tools for Visual Studio Code
Changelog for PowerShell Pro Tools for Visual Studio Code
- Updated version of PSScriptPad
- Fixed an issue where specifying an icon with the IronmanPowerShellHost would cause the executable to fail to run.
- Added support for specifying any .NET or PowerShell 7 version to package
- Fixed an issue where the IronmanPowerShellHost would truncate the first 3 characters
- Fixed an issue where the IronmanPowerShellHost would not accept arguments
- Fixed an issue where the IronmanPowerShellWinFormsHost wouldn't run anything
- Fixed an issue where the Ironman PowerShell Host wouldn't properly set $PSScriptRoot
- Fixed an issue where the form designer would not open
- Removed license check for several features in the PowerShell Pro Tools Activity pane
- Fixed an issue where the packager wouldn't correctly pacakge scripts with Unicode characters
- Fixed an issue where unsigned DLLs were not loaded successfully when packaging executables
- Fixed an issue where PSScriptPad failed to launch from VS Code.
- Added Ironman Software host for packaging
- Fixed an issue where the variable explorer would be empty
- Added PowerShell Performance output
- Fixed an issue where bundled assemblies would cause unexpected output in executables
- Added support for packaging PowerShell 7.2.5 and 7.2.6 executables
- Added support for switch parameters with Convert To Splat
- Added support for packaging PowerShell 7.2.4 executables
- Fixed an issue where the extension would fail to activate.
- Fixed an issue where license files were not correctly validated
- Removed a duplicate license key install command that did not work
- Fixed an issue where the icon was incorrect for PowerShell Pro Tools
- Fixed an issue where the form designer would not be shown even when the setting was enabled.
- Added settings to hide the buttons in the toolbar
- Added support for packaging PS 7.2.3
- Fixed an issue where non-ASCII characters wouldn't be stored correctly after packaging
- Fixed an issue where licenses could not be applied through the UI
- Fixed an issue where the welcome page would be blank
- Fixed an issue where an exception would be thrown when moving arguments
- Fixed a typo in the introduce using namespace refactoring
- Fixed an issue where Generate Proxy Function would add an additional blank line on Windows
- Fixed an issue where Rename Symbol would not work properly
- Fixed an issue where Use parameter splatting wouldn't work with switch parameters
- Fixed an issue where Use parameter splatting wouldn't work for commands line a pipeline
- Fixed an issue where providers would not load correctly
- Removed code conversion features
- Added support for MacOS ARM64
- Fixed an issue where the extension would not load properly on MacOS or Linux
- Fixed an issue where PowerShell 7.2 executables would not work as a service
- Fixed an issue where PowerShell 7.x executables would not have an icon
- Fixed an issue where PowerShell 7.x executables would not elevate properly
- Added Extract Variable refactoring
- Fixed an issue where a script compiled as a service would fail to run
- Fixed an issue where obfuscated builds wouldn't work twice
- Fixed an issue where obfuscated Windows PowerShell builds wouldn't execute correctly
- Fixed an issue where PowerShell 7 executables would not have file properties
- Fixed an issue where packaging a PowerShell 7.2 or later executable could result in a failure to build
- Fixed an issue where an attempt to load missing assemblies would be made.
- Fixed an issue where packaging an executable into an output directory with an apostrophe does not work.
- Fixed an issue where PS7.1 and PS7.2 output directories would contain all unpackaged files
- Added support for packaging PowerShell 7.2 and .NET 6.0 executables
- Added support for renaming the output executable
- Reduced the size of the extension by 80%
- Windows ARM platform support
- Support for bundling PowerShell 7.1 scripts
- Support for the Microsoft PowerShell Preview extension v3
- Support for signing executables
- Fixed an issue where PSScriptPad would hang when saving a large file
- Fixed an issue where the default WPF XAML would not work
- PSScriptPad will now open the designer and the form
- Fixed an issue where packaging in VS Code would use the wrong PowerShell SDK and fail to find modules
- Fixed an issue where the Upgrade-Module functionality would silently fail
- Fixed an MSBuild warning that was shown when compiling on Windows
- Added support for bundling additional XAML files in executables
- Fixed an issue where using the .NET 5 SDK would cause executables to fail to build on Windows
- Added support for switching the .NET SDK to use for packaging.
- Added better error handling to console host to prevent packaged applications from crashing and to provide a meaningful error
- Added support for excluding automatic variables from variables view
- Fixed an issue where DataGridView columns could not be added to the form designer
- Fixed an issue where the packager would fail when the script name had a space in it
- Fixed an issue where an exception could be thrown during packaging.
- Added support for bundling resources into executables
- Fixed an issue where the extension would not activate
- Fixed an issue where workspace analysis could prevent other features of the extension from work in tandem
- Fixed an issue where the History node was slow
- Fixed an issue where the PowerShellProTools.Host.exe process would constantly use CPU
- Added support for packaging PowerShell 7.0.6
- Updated to latest .NET Core SDK to remediate CVE-2021-26701
- Fixed an issue where Rename Symbol (F2) would incorrectly rename variables
- Fixed a performance issue with workspace analysis
- Fixed an issue where the extension could fail to load on some Windows system
- Fixed an issue where the extension could fail to load in large workspaces
- Fixed an issue where PSScriptPad would crash when pressing Ctrl+C
- Add support for disabling QuickEdit during packaging
- Fixed an issue with the packager and strings with single quotes
- Fixed a packaging issue with concatenated strings and Join-Path
- Fixed an issue with extension activation
- Fixed an issue with generating ImageLists in PSScriptPad resources
- Fixed a crash on startup in PSScriptPad
- Resolved a performance issue where analysis would run twice in PSScriptPad
- Updated version of PSScriptPad
- Added Open with PSScriptPad to PS1 files navigation bar
- Added F2 Rename Variables
- Fixed an issue where the extension would fail to activate on Linux and Mac OSX.
- Updated PSScriptPad version
- Removed custom telemetry setting to rely on the built-in, opt-in VS Code setting
- Fixed an issue where the extension could hang during activation
- Fixed an issue where string resources would not be output in the form design
- Fixed an issue where the extension could fail to activate
- Added Jobs explorer and management
- Added session explorer
- Added pin and unpin session commands
- Fixed an issue where the VS Code module wouldn't load properly
- Fixed an issue with several links within the extension
- Added support for custom tree views
- Added history view to PowerShell Explorer
- Improved extension activation performance
- Improved status bar message icon visibility
- Added namespaces to the reflection view
- Added a command for loading assemblies into the reflection view
- Added type decompiler to Reflection view
- Improved field and property information in Reflection view.
- Added Reflection view
- Added Sign on Save feature
- Fixed an issue with activation caching
- Fixed an issue with packaging PowerCLI
- Fixed an issue where packaging modules could cause an Access Denied error
- Added subscription activation caching to prevent excessive web requests
- Fixed an issue where packaging would use the wrong PowerShell version when looking up modules causing certain modules to fail to load
- Fixed an issue where the Introduce Using refactoring could cause the PowerShell Pro Tools host to stop responding
- Removed an unnecessary and noisy log message.
- Updated the version of PSScriptPad
- Added 'Open PSCommander Configuration' Command
- Added a setting for the license key so that licensing works with Settings Sync.
- Added support for building .NET Core based Windows Services with PowerShell 7
- Fixed an issue where packaging would not work with modules that contained a C# .cs file (like MSAL.PS)
- Added support for Packaging on Mac OSX
- Fixed an issue where arguments would not be passed to packaged scripts running PowerShell 7
- Fixed an issue where an error could be shown in the console when navigating PowerShell scripts.
- Fixed an issue where an error would be shown when the VS Code automation feature could not connect properly
- Fixed an issue where an invalid link would be shown in the hover provider.
- 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
- 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.
- Fixed an issue with convert to $_ and convert to $PSItem refactorings
- 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
- 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
- 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
- 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.
- 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
Changed
- Fixed an issue where the profile would run within the PoshTools host process rather than in the PowerShell process.
Changed
- Fixed an issue where packaging would fail with a duplicate assembly error
Added
- Added support for Mac OS
Changed
- 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
Changed
- Fixed an issue in PSScriptPad where variables would not be shown during debugging.
Changed
- Fixed an issue with bundling the ActiveDirectory module in PowerShell 7 standalone executables
Added
- Support for Linux
Changed
- Fixed an issue with packaging Windows Forms applications with PS7
Added
- Added support for packaging the 7.0.2 and 7.0.3 PowerShell SDK
Changed
- Default install of trial license
Added
- Added "Generate Tool" command
Changed
- Updated to the latest version of PSScriptPad
- Fixed an issue with Form Generation where it would generate forms with common parameters
Added
- PowerShell Pro Tools: Install PowerShell Pro Tools Module command
Changed
- Fixed an issue that would cause the extension to delay on startup and occasionally time out
Changed
- Fixed an issue with PSScriptPad where the variables window wouldn’t expand variables correctly
Changed
- Fixed an issue that would cause a delay on start up
Changed
- 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.
Changed
- 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
- 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
Changed
- Fixed an issue where the extension could fail to connect to the PowerShell process.
Changed
- The provider tree view now runs within the main runspace.
Added
- Added Host Processes tree node with support for one-click debugging runspaces
Added
- Added an Output Channel for PowerShell Pro Tools diagnostics
Changed
- 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
- Added support for packaging PowerShell 7 executables
- Added experimental support for packaging Linux and OSX executables
Changed
- Fixed an issue with PSScriptPad that was causing hangs when running WinForm scripts.
Added
- Out-VSCodeGridView
Added
Changed
- 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
Changed
- 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
Changed
- Fixed an issue with the variable view not showing variables.
Added
– 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
Changed
– 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
- 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
- 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.