I had assumed that the Windows PowerShell ISE is a take-it-as-it-is ISE (Integrated Scripting Environment) or IDE (Integrated Development Environment).
But a very helpful response (to a previous question I posted) …
… inspired me to ask if there is some way to add utilities to the Windows PowerShell ISE, such as, for example:
A toolbar item (or a keystroke) to comment or uncomment a block of lines;
To sort lines alphabetically;
To trim white space;
To create tools. For example, in another IDE (EditPadPro) I coded a “tool” that calls a script that makes a .rar archive copy of the current version of the PowerShell script on which I am working. I wish I could have the same tool available I am using the Windows PowerShell ISE.
Maybe the Windows PowerShell ISE is just a take-it-as-it-is ISE (Integrated Scripting Environment) or IDE (Integrated Development Environment), and no such embellishments can be made. But I thought that there’s no harm in asking.
There has been a software called ISESteroids, but since MSFT stoppped the development of the PowerShell_ISE I’d expect the AddOns - if they still exist - will disappear soon as well. Especially since the PowerShell_ISE is not able to work with PowerShell core out of the box.
There are numerous plugins for VSCode for alomst every thinkable purpose. I’d recommend to focus on that modern and actively developed IDE.
That’s only available for questions with the category “PowerShell Help”. But since the question was not actually about PowerShell code I categorized it as “Open Discussion” and “shell-business”.
I have a paid license for IseSteroids. I don’t use ISE to write the bulk of my code - for that I either use Notepad++ or Visual Studio Code.
Where I do still use ISE and IseSteroids is when I plan on releasing a script to others I use its syntax checking to catch and ensure that parameters are called explicitly with the actual name of the parameter and not a shortening of it. I believe that a script that is given to others it should not contain any aliases and every parameter should be used explicitly and not use parameter position to properly parse and execute the command line.
Hello,
As it is an open discussion …
I admired this afternoon as PowerShell ISE has nice features, and readable fonts without doing anything for that (except for the list of cmdlets), which is not that frequent on Windows 10/11.
It would be a good idea Microsoft abandons IE and Edge, that would leave them time to clean up things when needed, for instance update of the PowerShell help system.
The PowerShell_ISE is not actively developed anymore and only supports Windows PowerShell (5.1). MSFT invests all efforts into VSCode now. It is highly customizable and much much more advanced than the old PowerShell_ISE.
They already did that.
While it’s actually off topic for this thread … what kind of update would you expect for the help system?
Just after having typed Update-Help (and waited for it to execute of course), in PowerShell ISE I selected Compare-Object in the select interface on the right.
Then I clicked on the blue question mark help button.
It displayed a help for Compare-Object, with a readable font which is somewhat exceptional on Windows 10/11, but it ends with a remark, that begins by something like “Get-Help cannot find the help files for this command applet on this computer. It only finds a partial one.”
Again … PowerShell_ISE reached its end of life actually. There will not be any improvements anymore.
If you want to display the help for any cmdlet or topic in a separate window you can use the parameter -ShowWindow from any console (version 5.1 or 7.x). For example:
And you can even zoom in or out in this window with <Strg>+<+> and <Strg>+<-> or by holding the <Strg> key and using the mouse wheel. How about that?
Or if you could use the parameter -Online what opens the help topic in a browser tab of your default browser.
Get-Help Compare-Object -Online
With either way you have the advantage not to pollute your console window with a lot of text you need to scroll up and down.
I know this is an old thread, but I as well have a paid for subscription to ISESteroids. My sole use for the add on is to build an EXE. It is by far the best tool I have used to get this done for Windows PowerShell, not to mention the author is EXTREMELY good at getting back to you in e-mail if you have questions. He even helped me get an EXE built for PowerShell 2.0. The dude is amazing.