incorrect link to PowerGUI 3.2 on the home tab

Feb 1, 2013 at 12:34 AM
Edited Feb 2, 2013 at 4:51 PM
The PowerGUI 3.2 link points to, which is currently for 3.5. This is unnecessarily confusing as it results in downloading PowerGUI 3.5 only to get a popup from the 1.5.5 VSX saying it requires 3.2 and can't work with 3.5.

Looks like the correct link is This is not easy to find as there's apparently no link to it at and searching for 3.2 at does not yield any hits. But fortunately Bing indexes the 3.2 download page.

Also, the VSX installer help text seems to be a little misleading. It says to close and restart all VS instances for the VSX to be picked up. Restarting any one VS instance seems sufficient for the VSX to be picked up in that instance but the extension does take effect for .ps1 files that were open in VS prior to the install. You also have to close and reopen any open PowerShell files to get fontification, intellisense, and so on; seems there's probably a bug with the extension where it doesn't correctly hook load of a file that was remembered as open.
Feb 2, 2013 at 4:16 PM
took me a second, there is a period at the end of the above link to the 3.2 download, below is an updated version of the link, thanks so much for the point in the right direction.

Adam, is there anyway that you could get redist rights for the versions of the powergui msi and then post them with the downloads so that they aren't so hard to find?
Feb 2, 2013 at 4:52 PM
Yeah, greedy linkification and resulting incompatibility with proper punctuation is a common bug in posting software. Fixed the original post (the workaround is to explicitly insert the link using the insert link button rather than simply pasting it in).
Feb 7, 2013 at 2:28 PM
Hey guys, nice catch. Very soon I hope to have a build on here that supports 3.5. Sorry for the delay. I really wish I could just package up the pieces of PowerGUI that make this extension work but I'm not sure that is feasible. Let touch base with the PowerGUI team and see if there is anything we can do to make this process a bit easier. Having to install 2 things to get this extension to work is pretty annoying.
Feb 12, 2013 at 12:37 AM
It looks like it won't be possible to do this. Legal complications and what not. Would have been ideal.