“Notepad for PowerShell” – PowerGUI 1.0.11 is out

PowerGUI 1.0.11 is out and can be freely downloaded from PowerGUI downloads page.

This is probably one of the most community-driven releases we had. Most of the features are implementations of enhancements and fixes suggested by the PowerGUI community and the key features – stand-alone PowerShell script editor is no exception.

That’s right, now you can use the script editor we introduced in 1.0.9 not just for PowerGUI node, actions, and links but also for any ps1 files on your disk:

PowerGUI free PowerShell script editor

The editor has all you would expect:

  • Syntax highlight,
  • Intellisense for PowerShell cmdlets and cmdlet parameters,
  • Tooltips with syntax information,
  • Matching brackets, search/replace, regions,
  • Ability to export, run, print, etc.

And more importantly we tried to do our best to add these goodies without sacrificing the advantages of the main PowerShell editor on the market today – Windows Notepad. The script editor:

  • Is absolutely free (installs as one of the features of PowerGUI), and
  • Is very lightweight and fast.

(I know that bundling it with Windows would have been even better but I am not sure EU would have allowed us to do that. ;))

Thanks to the PowerGUI community and especially Kirk the Poshoholic and Richard Siddaway (from PowerShell UK UG) for pushing us into that direction.

Tags: ,


22 Responses to ““Notepad for PowerShell” – PowerGUI 1.0.11 is out”

  1. 1 halr9000 October 8, 2007 at 6:10 pm

    Dmitry, this is awesome! Code folding!

  2. 2 dmitrysotnikov October 8, 2007 at 6:56 pm

    Completely forgot about that one. 🙂 Yep, we got it too. Thanks Hal!

  3. 3 Greg M October 9, 2007 at 6:30 am

    Wow. Can’t wait to get to using this. Too cool.

  4. 4 mcgurk October 9, 2007 at 12:56 pm

    Download is fuxzored.

  5. 5 dmitrysotnikov October 9, 2007 at 1:06 pm

    Please try again a bit later – I’ve just downloaded myself and it worked with no issues whatsoever. I am guessing that the servers might be quite loaded because everyone is trying to get the new version.

  6. 6 Bob October 9, 2007 at 4:09 pm

    It looks really cool, great job!


  7. 8 Trevor June 26, 2008 at 5:17 pm

    This is a great tool considering Powershell Analyzer is the only real competition and it costs almost $100. One question, is there any plans to improve the performance? I see a lot of lag from keystroke to appearance.

    At any rate, thanks for the link!

  8. 9 dmitrysotnikov June 27, 2008 at 7:26 am


    Any repro steps? What was it that you typed which caused the delay?


  9. 10 Trevor August 20, 2008 at 4:59 pm

    Hi Dmitry, it happens when typing anything. It is most noticable when going from line to line, but also with normal characters. The script I notice it most with is well over 1000 lines so I’m guessing that has something to do with it but still notice it in short scripts as well.

    Another issue I’ve noticed is it keeps asking me to upgrade to version, I let it install, it shuts down, and I restart the app. Next time it asks me to do the same thing all over again so the upgrade appears to not “stick.”

  10. 11 dmitrysotnikov August 20, 2008 at 6:16 pm


    You can improve the performance of syntax highlight for large files by using the patch published by Alexey here: http://powergui.org/thread.jspa?threadID=7082&tstart=0

    As for the upgrade, yes, unfortunately this is an issue with 1.5.0. The editor downloads the new update but does not initiate the upgrade. Try one of the following:

    * Start PowerGUI admin console instead of the editor – it should perform automated upgrade just fine.


    * Manually download the setup from PowerGUI.org and run the setup file.


  11. 12 Trevor August 27, 2008 at 6:11 pm

    Thanks for the help, I think there’s something wrong with the .xml provided in that link though. My end brackets around datatypes trigger newlines and suck $’s into the brackets. 🙂

  12. 13 Dmitry Sotnikov August 28, 2008 at 12:25 pm


    This is a known issue of 1.5.1: http://powergui.org/thread.jspa?threadID=7340&tstart=0 – which is already fixed in internal builds, and will be no more in 1.5.2 to be out in just a few weeks.

    For now the workaround is to not type the opening bracket. Just type:


    And the editor will automatically insert the opening bracket as well.


  13. 14 Pawakumar Jajara July 13, 2011 at 12:20 am

    Good Job !

    I found it very helpful working on Power Shell for the first.

  1. 1 MiVanVelem - Karikatúra, IT, hétköznapok » Az erő velünk van Trackback on October 9, 2007 at 9:12 pm
  2. 2 PowerShell Editor | Ramblings from The Montopolis Group Trackback on October 10, 2007 at 3:09 am
  3. 3 PowerScripting Podcast - Episode 10 « PowerScripting Podcast Trackback on October 15, 2007 at 1:46 am
  4. 4 PowerShell Highlight for your Blog « Dmitry’s PowerBlog: PowerShell and beyond Trackback on October 16, 2007 at 8:22 am
  5. 5 [MSFT-BE] Arlindo's Blog - IT Pro Evangelist : Some PowerShell Stuff Trackback on October 26, 2007 at 7:12 am
  6. 6 New free PowerShell debugger « Dmitry’s PowerBlog: PowerShell and beyond Trackback on November 20, 2007 at 5:51 pm
  7. 7 Az erő velünk van - Exchange Server 2007 / 2010 - TechNet Klub Trackback on August 11, 2010 at 8:53 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

My Recent Tweets


The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

October 2007

%d bloggers like this: