I just finished releasing the bits for PowerGUI Pro 2.2 and PowerGUI 2.2 to the web. This release contains some really useful updates to PowerGUI, most notably a new debugging engine based on the native PowerShell 2.0 debugger. This allows you to do take advantage of all of the debugging functionality in PowerShell 2.0, including support for:
- The Disable-PSBreakpoint, Enable-PSBreakpoint, Get-PSBreakpoint, Remove-PSBreakpoint and Set-PSBreakpoint cmdlets;
- Command and variable breakpoints;
- and more
For basic debugging support of a single script file you might not notice a difference right away, but if you do anything beyond basic scripting the new debugging engine will be a welcome change. It allows you to set breakpoints in a module that you have loaded or a script file that you have dot sourced, and the debugger will open the file with the breakpoint if it is not already open and stop on the breakpoint when the breakpoint is hit. It also allows you to debug module scripts themselves by setting a breakpoint within a module psm1 file and loading the module using the Import-Module cmdlet from the embedded PowerShell Console. Breakpoints are retained between sessions as well, so that you can pick up where you left off day after day.
In addition to the debugger changes, there are a number of useful bugfixes included in this release such as improved compatibility between the PowerGUI Script Editor and the Quest AD cmdlets when using STA mode (the default), proper $MyInvocation support in scripts, and other fixes that allow Start-Job and Invoke-Command to be used in scripts that are run through the debugger.
To get the latest release, if you are a PowerGUI Pro customer you can visit SupportLink to get the most recent version or if you use the freeware version you can visit the PowerGUI Downloads page and download and install the release from there. Alternatively, for both PowerGUI Pro and PowerGUI freeware you can simply wait until auto-update kicks in and prompts you to upgrade (auto-update checks for a new version once per day, the first time you open the product each day), or you can use the Help | Check for Updates menu item in the Admin Console or Script Editor to check for updates without waiting for the next time it checks automatically.
Note to 2.2 public beta testers: if you were participating in the PowerGUI 2.2 public beta, and if you upgraded your beta install to the release candidate when we had posted it, then you already have the RTM version of PowerGUI. We collected feedback during the release candidate stage and did our own internal testing and the release candidate was solid enough that we were able to leave it as is. This means that you don’t have to do anything to upgrade to the 2.2 release in this case.
As always, if you have questions, comments, concerns, we’re always listening. Please let us know what you think of the new capabilities that are introduced with the new debugging engine!