PowerShell Tools for Visual Studio

Free

PowerShell integration for Visual Studio

(32) Review
Visual Studio
2013, 2012
Download (51,510)
2/21/2014
0.7.2
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (32)
Q and A (44)
Sign in to write a review
Sort by:

by Matt Wrock | Mon 6:49 AM

Awesome extension. Great work here!

by Ivan_Shakhov | April 14 2014

Excellent tool.
However
1. After long time I have found "execute as script", I was definitely expecting it in the SolutionExplorer. It lacks asking for mandatory parameters.
2. There is a project structure, but no intellisense for calling one script form another, like
& "$ProductHomeDir\PowerOff.ps1" -cloneNamePattern $cloneNamePattern

by Guido Basilio de Oliveira | April 04 2014

Exelent Tool, you should keep up the developmemnt

by Kurt Congdon | April 03 2014

Very cool! Keep up the great work

by Lee Berg | March 21 2014

Five out of Five.

Our team is using TFS to manage PowerShell scripts we use in our various projects. Being able to work with scripts directly in Visual Studio and interact with TFS is a great workflow!

Adam R Driscoll March 29 2014
| Edit |
Delete

Thanks, Lee!

by Rob Plank | March 13 2014

by bgoldsht | February 24 2014

Adam,
looks like you forgot to include VS2013 as a target in 0.7.2
I am getting [ERROR] Resolve-Path : Cannot find path 'C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\&' because it does not exist. I have only VS2013 installed.

After downgrade to 0.7.1 all works again.

Thanks.

Adam R Driscoll March 23 2014
| Edit |
Delete

Dang. Will have to look into that.

by Matt Watt | February 24 2014

0.7.2 throws an exception in VS 2013 Ultimate. Win7 x64

"SetSite failed for package [PowerShellToolsPackage]"
"Exception has been thrown by the target of an invocation."

by John Ludlow | February 21 2014

Good stuff!

Some suggestions which I think could make it better: Make intellisense work
more like Visual Studio (ctrl-space rather than tab)), and add options for
generating help and tests for modules and functions.

But otherwise, great! :)

by Adrian Faciu | February 13 2014

by wonderblast1 | January 27 2014

by Fakher Halim | January 25 2014

I was dying to see some tool like this.
We guys spend almost 8 hours a day in front of Visual Studio, yet to do PowerShell, we had to move out of it,
and click other third party Tools (or ISE). What a distraction!

I wish they do a little more to support this forgotten area of serious developer tools development.

by Alexander Romanov | January 14 2014

by Matthias Einig [MVP] | January 09 2014

Awesome work! Thanks!

by sluggie | December 13 2013

This tool is great! I can stay in Visual Studio and not have to switch out to another tool for PowerShell

by BI Admin (Bryant E. Byrd) | December 12 2013

This is a fantastic tool. It's important for me to be able to keep my PowerShell scripts in a common solution with my other projects. This makes it easier to do that since the editor is now integrated right in VS.

Thank you!

by Isaac Rainsford | December 07 2013

Keep up the great work.

Spectacular.

by kelley | December 03 2013

Top notch stuff! Keep up the good work!

by omendezmorales | November 28 2013

The extension is definitely worth including it in the official version of VS, which happens to be a very decent IDE and text editor -text being the very DNA of everything we do when making software. Kudos to Adam for this fine work ;-)

by Si Vane | November 07 2013

This is a great extension and the developer is very fast at responding to issues. Also, I'm not aware of anything else like it available. Should be built into VS really.
Thanks.

1 - 20 of 32 Items   
Sign in to start a discussion


  • Syntax Highlighting
    5 Posts | Last post Mon 2:24 PM
    • Why doesn't my syntax highlighting look as good as yours in the screenshot?
      
      http://i.imgur.com/H62lZyd.png
    • Have you tried adjusting your coloring in the Fonts and Colors dialog?
    • I'm afraid that will change syntax highlighting for other languages as well. As far as I can remember, all the values there should be a their defaults.
      
      Did you change anything to achieve the highlighting in your screenshot? I was hoping the add-in would define its own syntax highlighting schema for PowerShell scripts, but I don't really know how all this works behind the scenes.
    • I do have the same issue and wonder if anyone of you found a solution for it?
    • There are items just for PowerShell. 
  • Input parameters
    2 Posts | Last post Mon 2:23 PM
    • i've created a .ps1 script requiring mandatory parameters; is there a way to debug the script with reuired parameters?
    • On a PowerShell project you can specify arguments to pass the debugged script. What I really need to implement is a tool bar or something where you can enter these...
  • 0.7.2 fails with powershell 4 on vs 2013 & 2012
    2 Posts | Last post April 11, 2014
    • VS 2013..
      
        <entry>
          <record>179</record>
          <time>2014/04/11 05:44:36.612</time>
          <type>Error</type>
          <source>VisualStudio</source>
          <description>SetSite failed for package [PowerShellToolsPackage]</description>
          <guid>{58DCE676-42B0-4DD6-9EE4-AFBC8E582B8A}</guid>
          <hr>80131604</hr>
          <errorinfo>Exception has been thrown by the target of an invocation.</errorinfo>
        </entry>
        <entry>
          <record>180</record>
          <time>2014/04/11 05:44:36.721</time>
          <type>Error</type>
          <source>VisualStudio</source>
          <description>End package load [PowerShellToolsPackage]</description>
          <guid>{58DCE676-42B0-4DD6-9EE4-AFBC8E582B8A}</guid>
          <hr>80131604</hr>
          <errorinfo>Exception has been thrown by the target of an invocation.</errorinfo>
        </entry>
      </activity>
      
      VS2012...
      
        <entry>
          <record>229</record>
          <time>2014/04/11 05:55:35.307</time>
          <type>Information</type>
          <source>VisualStudio</source>
          <description>Begin package load [PowerShellToolsPackage]</description>
          <guid>{58DCE676-42B0-4DD6-9EE4-AFBC8E582B8A}</guid>
        </entry>
        <entry>
          <record>230</record>
          <time>2014/04/11 05:55:35.358</time>
          <type>Error</type>
          <source>VisualStudio</source>
          <description>SetSite failed for package [PowerShellToolsPackage]</description>
          <guid>{58DCE676-42B0-4DD6-9EE4-AFBC8E582B8A}</guid>
          <hr>80131604</hr>
          <errorinfo>Exception has been thrown by the target of an invocation.</errorinfo>
        </entry>
        <entry>
          <record>231</record>
          <time>2014/04/11 05:55:35.358</time>
          <type>Error</type>
          <source>VisualStudio</source>
          <description>End package load [PowerShellToolsPackage]</description>
          <guid>{58DCE676-42B0-4DD6-9EE4-AFBC8E582B8A}</guid>
          <hr>80131604</hr>
          <errorinfo>Exception has been thrown by the target of an invocation.</errorinfo>
        </entry>
      </activity>
    • Can you try installing either the VS2012 or VS2013 SDK? 
  • Error while starting Visual Studio 2013: The 'PowerShellToolsPackage' did not load correctly.
    14 Posts | Last post March 31, 2014
    • I installed this extension and after restarting Visual Studio I got the following message:
      ---------------------------
      Microsoft Visual Studio
      ---------------------------
      The 'PowerShellToolsPackage' 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 examining the file 'C:\Users\[...]\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml'.
      
      
      
      Continue to show this error message?
      ---------------------------
      Yes   No   
      ---------------------------
      
      In the ActivityLog.xml I found the following entries:
       <entry>
          <record>239</record>
          <time>2013/12/10 14:53:56.799</time>
          <type>Information</type>
          <source>VisualStudio</source>
          <description>Begin package load [PowerShellToolsPackage]</description>
          <guid>{58DCE676-42B0-4DD6-9EE4-AFBC8E582B8A}</guid>
        </entry>
        <entry>
          <record>240</record>
          <time>2013/12/10 14:53:56.833</time>
          <type>Error</type>
          <source>VisualStudio</source>
          <description>SetSite failed for package [PowerShellToolsPackage]</description>
          <guid>{58DCE676-42B0-4DD6-9EE4-AFBC8E582B8A}</guid>
          <hr>80131604</hr>
          <errorinfo>Exception has been thrown by the target of an invocation.</errorinfo>
        </entry>
        <entry>
          <record>241</record>
          <time>2013/12/10 14:53:56.833</time>
          <type>Error</type>
          <source>VisualStudio</source>
          <description>End package load [PowerShellToolsPackage]</description>
          <guid>{58DCE676-42B0-4DD6-9EE4-AFBC8E582B8A}</guid>
          <hr>80131604</hr>
          <errorinfo>Exception has been thrown by the target of an invocation.</errorinfo>
        </entry>
      
      
      I am using Visual Studio Premium 2013
      Version 12.0.21005.1 REL
      
      Best regards,
      Stefan
    • That's no good! What OS are you running on? 
    • I'm on Windows 7 Professional SP1 (64 Bit).
    • Do you have PowerShell v3 installed? 
    • No, I don't think so. 
      
      Sorry, I missed that requirement.
      
      In my C:\Windows\System32\WindowsPowerShell folder is only one subfolder named "v1.0".
      
      Looks like I'm 2 versions behind. I'm just starting developing with powershell. 
      
      
    • You can get it here: http://www.microsoft.com/en-us/download/details.aspx?id=34595
      
      The folder doesn't actually change from v1 so you are probably running v2. ;) 
    • >You can get it here: http://www.microsoft.com/en-us/download/details.aspx?id=34595
      
      Thanks, I will check whether an update is an option for our team.
      
      >The folder doesn't actually change from v1 so you are probably running v2. ;)
      
      Oh dear...
    • I get this error in vs2012 after installing PowerShell v4
    • Interesting. I'll need to look into that. I'm pretty sure some people are running Powershell v4 successfully but will test with your configuration to see if I can reproduce. 
    • Let me know if there's anything I can do to help, Powershell ISE really bites :)
    • Actually, I found your source on github and downloaded it, but found that I needed the vs2012 sdk to open it.  After installing the sdk, I found that the error no longer occurs, so there must be a dependency on the sdk?
    • Oh, now that's interesting. I'll have to give that a shot on a clean machine of mine to see if I see the same thing. 
    • Thanks for the tip S Williams, after installing the SDK I am able to use the module with VS 2012 Update 4 on Win 7 x64.
    • Same issue on Windows 7, Visual Studio 2013, VS 2013 SDK, Windows Management Framework 4.0
  • Does this only work if you have a script file in a solution file
    2 Posts | Last post March 30, 2014
    • At first I started opening my ps1 or psm1 files in VS2013 and it would not give me intellisense and run options.  Then I gone and created a new sln and that when everything working.  So why do I need to make a solution/project file to make the powershell option work?  It no big deal but had to ask.
    • That's interesting. I should certainly work on any PS1 or PSM1 file that you open, regardless if there is a project involved. I'll have to take a look. 
  • Running Pester
    2 Posts | Last post March 29, 2014
    • This extension is getting better and better. I was please to see that it supports testing with Pester. But I'm having an issue.
      
      The latest drop of Pester has been installed in the Module path (I can Invoke-Pester from a PowerShell window just fine). And the tests that I have in my project are detected and listed in the Test Explorer window. But when I click on Run All (tests), they all fail with "The term 'Invoke-Pester' is not recognized...". 
      
      What am I missing?
    • Hmm that's no good. Let me take a look. 
  • How does 'Script Arguments' work? (or does it?)
    2 Posts | Last post March 29, 2014
    • Fantastic tool, thank you!
      
      Question.. how does the Debug->Script Arguments setting work? I've entered an argument there, loaded my script, selected 'execute as script', but the arg isn't set when the script runs. Is there something I'm missing? Is it a problem if I have 50 or so script files in the project?
      
      Thanks!
      Chris
    • Sounds like a bug. Could you log it on GitHub?
  • SharePoint
    2 Posts | Last post March 29, 2014
    • Is it possible to load the Microsoft.SharePoint.PowerShell PSSnapin and use intellisense? Thanks
    • Not currently. This extension only supports x86 modules and snapins due to the architecture of Visual Studio. 
  • Do break points work in foreach?
    2 Posts | Last post March 29, 2014
    • I've been using Powershell Plus for years, but since the emmitter change in PS v3, Powershell Plus has been broken and remained unfixed when it comes to break points. Do break points work properly in VS 2012 with this extension?
    • They should! ;)
  • Remote Execution of PSScript
    2 Posts | Last post March 02, 2014
    • Hi. My Setup: 
      1 Notebook with Windows 7 Professional and Visual Studio 2013 Prof. 
      1 PC with Win Server 2008 R2 Enterprise
      Is there a way to execute the Scripts I write in VS13 on the Server with just the click on "Run" in VS13? 
      Thx.
      
    • Not yet. :) Something I need to investigate.
1 - 10 of 44 Items