Is there a way to add utilities to the Windows PS ISE?

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:

  1. A toolbar item (or a keystroke) to comment or uncomment a block of lines;
  2. To sort lines alphabetically;
  3. To trim white space;
  4. 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. :man_shrugging:t3:

There are numerous plugins for VSCode for alomst every thinkable purpose. I’d recommend to focus on that modern and actively developed IDE. :wink:


Thank you yet again. How do I indicate that you provided the “solution” or “answer” to my question?

I’m glad if it helped. :slightly_smiling_face: :love_you_gesture:t3:

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”. :+1:t3:

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.