PowerShell Tools for Visual Studio 2013


PowerShell integration for Visual Studio

(44) Review
Visual Studio
Download (94,473)
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Reviews (44)
Q and A (71)
Sign in to write a review
Sort by:

by Christian Thoenes | September 25 2014

This is awesome! Thanks a lot!

by Chandra Sekar Narayanan | September 25 2014

by Eugene Polonsky | September 12 2014

Very good tool. Good work, Adam!

by Jonathan Allen | September 04 2014

The only thing more I would like would be the ability to run scripts without having to first create a powershell project.

by Plinio B. Figueiredo | September 02 2014

by Ed (DareDevil57) | August 14 2014

by Ransher Singh | August 13 2014

Excellent addon for developers/system administrators alike.

by Thomas Freudenberg | August 09 2014

by Gemini Kris | June 27 2014

Amazing, simply works!

by Matthew Reynolds [MSFT] | June 26 2014

Thank you thank you thank you. Lately I find myself working on mixed C# / Powershell script projects, and being able to do everything directly in VS is awesome.

by Anthony Caragol | June 18 2014

Very nice, love to have this as an option!

by Ryan Mann (TLC) | May 09 2014

This tool works great, but you are running the powershell runspace in the AppDomain.

This causes issues for me because I am developing a powershell module and testing it in the IDE with a script.

So I right click the script and click execute, and it works great. But then I can build my powershell module because Visual Studio has the dll open still because the dll wasn't unloaded at the end of the script.

I suggest that you Create a separate app domain for the script to run in and when it's done (error and all) unload it.


Why don't you just have the executor run in a console app and use ProcessStartInfo to run it hidden and get it's output to write to the VS output window? You could compile the console app for x64 and x32 and make the right click execute script have two options "Execute 32" or "Execute 64"

Adam R Driscoll June 03 2014
| Edit |

This is actually a problem for me as well. :) The problem is with debugging. I need to have access to the variables, breakpoints and debugger state. My hope is to take advantage of the new remote debugging to work around this issue. It's certainly on my radar.

by Matt Wrock | April 21 2014

Awesome extension. Great work here!

by Ivan_Shakhov | April 14 2014

Excellent tool.
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

Adam R Driscoll June 03 2014
| Edit |

I love those ideas! Could you post them on GitHub??

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 |

Thanks, Lee!

by Rob Plank | March 13 2014

by bgoldsht | February 24 2014

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.


Adam R Driscoll March 23 2014
| Edit |

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."

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

  • Really need some documentation; Debugger does not work
    1 Posts | Last post Wed 8:28 PM
    • The complete lack of documentation is giving me some headaches. I'm using Visual Studio 2013 Ultimate, update 3. 
      First, my script requires startup arguments. Putting the values in the Script Arguments window does not work. I've tried this two different ways:
      -envConfigFilePath "D:\Code\Gem\Payment\dev\deployment\Configuration\environment.gem-dev-qa.config" -buildConfiguration "debug"
      "D:\Code\Gem\Payment\dev\deployment\Configuration\environment.gem-dev-qa.config" "debug"
      Neither works.
      Second, I tried creating a different script as that doesn't use parameters. The debugger does nothing. Oh it starts, puts Visual Studio into debug mode but nothing executes. Stop Debugging throws a Visual Studio exception -- "Unable to stop debugging. Operation not supported. Unknown error: 0x800400c3"
      Third, I tried to Debug Interactive. This runs the script and calls the imported scripts and functions but no breakpoints are hit.
      I'd really like to be able to use this tool and I'm hoping it has more functionality than the Windows Powershell ISE. It's just not working except as a code editor.
  • Breakpoint / steps don't work for me
    2 Posts | Last post Tue 1:40 PM
    • Hi.
      Installed under VS2013 Update 3, Win 8.1, running scripts works OK.
      When setting breakpoint and hitting F5 the script runs to completion, no debugging.
      When trying to press F10 or F11 to step into/over, again, the script runs to completing. 
      What did I miss ?
      PS1 file set as Compile
      VS mode set to Debug (Any CPU)
    • Try running VS as administrator. I was having the same problem, tried that, and now I am able to hit the breakpoints.
  • Powershell Tools Autoformat Code?
    3 Posts | Last post September 25, 2014
    • Hi, is it planned, that you implement a Way to AutoFormat the Code like the C++ Autoformat STRG+K+F Option in Visual Studio?
    • There is a basic formatter in there but it is by no means extensive. 
    • Not really comfortable, but thx. Powershell Studio 2014 from Sapien (unfortunately really expensive and a Standalone App) has this Feature, so maybe you will implement this?
  • Powershell 64-bit
    2 Posts | Last post September 23, 2014
    • Is there a way to get this tool to run the 64-bit version of Powershell?
    • Nope. Unfortunately, since VS is only x86, it can't run x64 PowerShell. 
  • SetSite Failed
    2 Posts | Last post September 16, 2014
    • When I try to start Vision Studio, I become a message that the plugin couldn't be loaded.
      I've uploaded my ActivityLog to Pastebin: http://pastebin.com/sftEggkA
      Windows 7 SP 1 Build 7601
      PS C:\Users\Jan> $PSVersionTable
      Name                           Value
      ----                           -----
      PSVersion                      3.0
      WSManStackVersion              3.0
      CLRVersion                     4.0.30319.18444
      BuildVersion                   6.2.9200.16398
      PSCompatibleVersions           {1.0, 2.0, 3.0}
      PSRemotingProtocolVersion      2.2
      I've installed the VisualStudio 2013 SDK, but it didn't help.
      There is also a Visual Studio 2010 installation on the PC.
      Any Ideas?
      Or do you need further information?
    • OK, I figured it out:
      I found following solution in the discussion of the Bug Report on gitHub:
      "This worked for me (clearing the ComponentModelCache folder at %LOCALAPPDATA%\Microsoft\VisualStudio\12.0)"
  • VS2013 Express for Web not supported?
    2 Posts | Last post September 12, 2014
    • The "free" version of VS suits my needs fine.  However, is there any reason why this version is not supported by PowerShell Tools for VS13?  Is there a workaround?
    • No one seems to be very active on the comments here but I figured I'd answer your question.  The "free" or express versions of Visual Studio do not support addins.  See this article http://blogs.msmvps.com/carlosq/2014/05/07/visual-studio-express-edition-doesn-t-support-extensions-despite-its-extension-manager/
  • Exchange PowerShell Support
    2 Posts | Last post August 27, 2014
    • Reading the other posts below this seems like a lame question, but I'm very familiar with Visual Stuido so I was wondering how I would go about adding support to use Exchange cmdlets within this environment. Typically I would add the snapin within the $profile but I don't know where to add it for this particular application
    • Supposed to read "I'm NOT very familiar with Visual Studio"
  • PowerShell Workflow Support
    1 Posts | Last post August 23, 2014
    • Greetings!
      Related to my last question - PowerShell workflows are not supported on the x86 console - how can we configure this project to Debug using the x64 console?
  • Open with PowerShell ISE 64-bit
    1 Posts | Last post August 23, 2014
    • I've noticed that when I have the 64-bit PowerShell ISE open already and Right-click a .ps1 file in my project and select "Open in PowerShell ISE," it uses the existing 64-bit ISE window.
      However, when the ISE is not already open, it defaults to the 32-bit ISE.  Is there a way to change this behavior?
  • Support for Powershell version 2 scripts possible?
    1 Posts | Last post August 22, 2014
    • Hi,
      I encountered the problem that powershell scripts for MS Sharepoint 2010 have to be run with Powershell version 2. Is it possible support this version of powershell as well?
      As I don't know what features of ver. 3 you use (and what has changed with v3), I can't say if it is sufficient to pass the argument "-Version 2.0" to the powershell.exe when executing the script using your plugin (could then be designed configurable in the plugin options).
      Here is a KB article which describes the limitation for sharepoint 2010 powershell scripts: http://support.microsoft.com/kb/2796733/en-us
1 - 10 of 71 Items