Your extension will be available shortly on the Visual Studio Marketplace at this link.



PowerGUI integrated into Visual Studio.

3.3 Star
Visual Studio
Download (52,716)
E-mail Twitter Digg Facebook
Add to favorites
Sign in to write a review
Sort by:

5 Star
by Anthony Caragol | June 18 2014

Works for me, a great option to have! I think I like hanging out in the PowerGUI interface just as much, since most of my development life is PowerShell these days.

2 Star
by Salvo Di Fazio | May 14 2013

1 Star
by rheid1globusfamilycom | March 28 2013

I love POWER GUI But this plug in will not work because I have 3.5 installed and the newest version of the plug only works with 3.2 and there is know where to down load the old version of the Power GUI

4 Star
by Richard_McIntyre | June 15 2012

Excellent, just need a VS12 version !

5 Star
by Dzmuh | December 14 2011

3 Star
by john.pea | December 08 2011

Shift+f5 is not working for me.

1 Star
by fkm | October 09 2011

Does not works on x64.
Any 64 bits Snapin ( as Microsoft.SharePoint.PowerShell) can be loaded in Powergui Script Editor (V3.0.0.2015 64bits) but cannot load in VS 2010 PowerGuiVSX (1.4.1)...

Adam Driscoll October 10 2011
| Edit |

Visual Studio is x86 and this is why it will not work with x64 snap-ins. This is a limitation imposed by VS and not PowerGUI. Sorry about that...

4 Star
by Rich Prescott | September 02 2011

1 Star
by Mike Chaliy | July 19 2011

Great idea, however it does not work:

Microsoft Visual Studio
The 'PowerGUIVsx.PowerGuiVsxPackage, PowerGUIVsx, Version=, Culture=neutral, PublicKeyToken=b7e1ba102ebba51e' package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by running the application together with the /log parameter on the command line, and then examining the file 'C:\Users\m\AppData\Roaming\Microsoft\VisualStudio\10.0\ActivityLog.xml'.

Continue to show this error message?
Yes No

Log file C:\Users\m\AppData\Roaming\Microsoft\VisualStudio\10.0\ActivityLog.xml does not exists.

Adam Driscoll August 01 2011
| Edit |

Hey Mike,

Do you have PowerGUI 3.0 installed? You'll need to install PowerGUI 2.4 if you do. We are working on 3.0 support right now.

You can download PowerGUI 2.4 here:

4 Star
by Matthew Manela | May 27 2011

4 Star
by Genady | August 12 2010

Outstanding. Code-folding on #region tags is pure WIN, and you can use the built-in VS TFS integration. My only issue is I can't get linenumbers to show up.

5 Star
by Dmitry Sotnikov | July 06 2010

Great to have PowerGUI Script Editor functionality right inside Visual Studio. Very handy for dev projects which includes PowerShell scripts.


Sign in to start a discussion

  • VS.NET Fonts and Colors
    2 Posts | Last post June 22, 2011
    • I use a non-standard set of Fonts and Colors for my VS environment. I'd truly love to see them reflected in the PowerGUI editor in VS.NET.
      Keep up the good work!
      p.s. if you want me to send you my Fonts and Colors VS settings file, just let me know.
    • I'd love to be able to modify the Fonts and Colors in VS. I'll make a CodePlex issue on it. Vote it up if you're interested!
  • Issues
    4 Posts | Last post June 22, 2011
    • I Installed version 1.3.5 on Visual Studio 2010 Ultimate. I am unable to get the syntax highlighting and code completion working. When I create a new powershell project it throws up an error "project type is not supported by this version of application".
    • Do you have the latest version of PowerGUI installed? You can get it here:
    • Yes I have PowerGUI 2.4.0 installed.
    • Is it the free version or Pro? If you have free installed could you try and grab a log of the issue? More information on the CodePlex site
  • 2 issues with VS 2010
    3 Posts | Last post June 21, 2011
    • - PS1 file do not trigger a TFS Check out when entering keystrokes
      - F3 to search next does not work.
    • The checkout issue is a bit frustrating for me as well, as it breaks my workflow.
    • Just checked in a fix for the TFS issue. That will be in the next version. Still working out the F3 issue. 
  • Text style is not consistent with either VS or PowerGUI
    3 Posts | Last post April 15, 2011
    • Most noticeably, the font is small an non-monospaced when using the plugin, but it's monospaced in PowerGUI and other code is monospaced in Visual Studio.
    • If you go into PowerGUI and click View->Font and then click Ok on the dialog. If you then open PowerGUI VSX it should have the correct font settings.  
    • Hi Adam
      I have the same issue, and that didn't fix it.
      (I presumed that when you said "go into PowerGUI", you were referring to the PowerGUI Script Editor external to Visual Studio ... since there is no View->Font menu option in VS)
  • The Device is not ready (Exception from HResult: 0x80070015)
    2 Posts | Last post March 25, 2011
    • I cannot install this extension, I get the result above. I have PowerGUI version 2.4 and I have run it once. I am running VS2010 Ultimate x64. Any ideas?
    • Could you turn on logging and shoot me the log? 
  • Unable to load PowerGUI components. Please install PowerGUI ....
    2 Posts | Last post February 17, 2011
    • I have a perfectly OK, running PowerGUI when in standalone (actually using it a lot). However, when in VS
      I am getting the above error, and a following 'Object reference not set to an instance of an object'.
      Is there any way to further diagnose this (a trace or an event logged)?
    • You can try turning on logging. Check out the documentation page: Let me know if anything useful comes from it. Thanks!
  • Expanding snippets?
    2 Posts | Last post January 15, 2011
    • When I try to add the PowerGui snippets VS 2010 says the file is invalid but gives no additional details.  If these snippets are already installed somehow, how to I expand them?
    • Sorry for the very late reply. I'm not quite sure why the snippet files are complaining that they are invalid. If they are already installed you should be able to press CTRL I to insert them. Give that a go and let me know the result.
  • Autocomplete on variables
    2 Posts | Last post January 15, 2011
    • [string] $var = "test"
      This will not give any options like "Length" etc which it will in a powershell prompt. Is this a planned feature, or is there a way to make it work?
      Mikael Svenson
    • This is fixed in 1.3 Beta 2. Grab it here:
  • Line numbers missing
    2 Posts | Last post August 27, 2010
    • I installed the PowerGUI extension in Visual Studio 2010 and now .ps1 files do not show line numbers, I cannot CTRL+G to go to a line number and Edit | Go To... is grayed out.
      Thoughts? It is a deal breaker for me to not have line numbers/Go To ability.
    • Hi Craig,
      This is a known bug and is fixed in betas after the version 1.0 stable release. Development will soon be ramping up again for getting those betas on track to be the next stable releases. 
11 - 19 of 19 Items