Skip to main content

Powershell ISE – Increase your productivity


For some time now I have been thinking about extending ISE to increase my productivity. Those of you that do heavy “powershelling” are probably already living inside ISEsteriods which is a terrific and professional extension. For all others this might suit your needs or maybe you will find it lacking in some areas.


On the top of my head? Why not. Microsoft has created a powerful environment for us which is free and lacking is some areas. Still with the update regime currently being the “defacto” standard there is no way they would satisfy the demanding needs you guys have. Secondly I was kind of curious if it could be done, and last but not least it was fun.


Please bear in mind that this is a alpha version 0.1 release and I know there are some issues with it, however it works and demonstrates the capabilities you can implement with very little efforts. I have organized the extension as a module which is built by my build.ps1 script. If you clone the repro and want to make it available in your modulepath, you only need to copy the psm1 and psd1 files in to a folder.

How does it work?

All you have to do is import the AutocompleteISE module in Powershell ISE. When you import the module it will create 2 menu items in the Add-on menu and link those to two keyboard shortcuts:
  1. ALT+3 will toggle comment for the current selectin (multiline commenting/uncommenting)
  2. F2 – will toggle autocomplete events in the scriptpane for the active/current script. Currently you have to actively enable autocomplete for each script-tab. This might change and is not an limitation in ISE.
Please see the readme file on GIT for a listing of autocomplete features currently supported. The readme also include a link to a youtube video showing the features.

Where are the unit tests?

Currently they are in my head. As I have previously stated, I like coding and powershell. Time is a precious constraint and I have been unable to find the time to do them. 


Look me up on twitter or file an issue on GIT and I will look into it. Also if you have suggestions or find a bug, be a good person and let me know.

Link to the repro: AutocompleteISE




Popular posts from this blog

Developing PowerShell modules for REST APIs – Part1

Over the years I have developed different PowerShell modules for different web APIs. I thought it would be a good idea to write a 2 series post about how you could go about to do this. This will be a 2 part blog series where we will run through the entire process of building a module for a REST API. I will try my best to keep this as simple as possible and leave more advanced stuff for a follow up post if the interest is there.What you needDepending on your experience with source control and PowerShell in general, you might want to use GIT or some other software repro for the code. In addition we are going to create a test REST API using the splendid UniversalDashboard PowerShell module created by Adam Driscoll. It is available on the PowershellGallery. Other prerequisites are built-in to Powershell. I will assume that you will be following along using at least PowerShell version 5 or greater.
What is HTTP metods for REST API.The primary or most common HTTP verbs used are POST, GET, PU…

Serialize data with PowerShell

Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData.

Other Serializing methods

In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in:
Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types:


You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate the same xml, however we …

Developing PowerShell modules for REST APIs – Part2

This is part 2 of the REST API blogpost. In part1 we successfully setup two REST API endpoints using the UniversalDashboard PowerShell module. In this part we are going to create a simple module that support some CRUD operation against our API. As we are trying to keep things as simple as possible, we will not use any fancy framework (like Plaster) to build our module. We are also going to skip a very important step you should familiarize yourself with, Pester tests. Lets get to it.

The moduleWe will build a module called FilesAPI. The module folder will look like this:

In the functions folder I have already added the 2 helper functions from part 1, Get-AuthorizationHeader and ConvertTo-Base64. The other folders are just placeholders for important stuff like classes, private functions that you do not want to make available for the module consumer and tests for Pester tests. For such a small module that we are going to create, one could argue that it is much easier to just add the functi…