Skip to main content

Powershell ISE – Increase your productivity


image

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.




Why

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.


Disclaimer

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. 


Questions/issues

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


Cheers

Tore

Comments

Popular posts from this blog

Monitoring Orchestrator runbook events from Operations Manager

Today I will follow up on my colleague’s post Mr ITblog (Knut Huglen) about monitoring Orchestrator Runbook events.  He has build a nice double up SNMP loopback feature that does self monitoring in Orchestrator resulting in entries written to a special Windows Eventlog. Now we need to raise alerts in SCOM when one of his runbooks fails or sends a platform event, who knows there could be trouble lurking in his paradise.

We are not going to do anything fancy, however these are the steps we will be focusing on today:
Create a Management Pack for our customizations Create rules that collects the events from the orchestrator serverOff we go then and fire up the SCOM console and a powershell window. First we create a MP, I am going to use powershell to do this, however you may use the SCOM console as well (Administration – ManagementPacks – Action: Create Management Pack):



Import the Management Pack into SCOM and move on to the Authoring section in the SCOM console. Create a new rule:



Give the…

Powershell – Log like you mean it

How do you do logging in powershell? Why should you do logging? What should you log? Where do you put your log? How do you remove your log? How do you search your log? All important questions and how you answer then depends upon what your background is like and the preferences you have. This will be a 2 part blog post and this is part 1.


Why should you log?

Well it is not mandatory, however I have 2 reasons:
Help with debugging a script/module/functionSelf documenting script/module/function
Firstly; Do you know any program that does not contain any bugs? Working with IT for the last 2 decades, I cannot name one. When you create scripts/modules/functions, you will create bugs, that is where they live and try to make your life a living mess.

Secondly: Adding a little extra information to your logging will make them self documenting. Do you like writing documentation? Well I normally am not fond of it and use logging while debugging to get two birds with one stone.


What should you log?

Anyt…

Powershell - List information about your WIFI networks

This is just a quick post about this new function I have created. Basically this is a text-output to powershell object output function that uses netsh to query the WIFI information. This illustrates the importance of changing the authentication level on your WIFI-network. No matter if you use WEP/WPA/WPA2 your password is available in clear text in your profile.



Cheers

Tore