PowerShell Tools for Visual Studio 2013

Free

PowerShell integration for Visual Studio

(39) Review
Visual Studio
2013
Download (84,151)
8/29/2014
1.0.2
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (39)
Q and A (65)
Sign in to write a review
Sort by:

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.

Edit:

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 |
Delete

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

Adam R Driscoll June 03 2014
| Edit |
Delete

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

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


  • Exchange PowerShell Support
    2 Posts | Last post Wed 7:56 PM
    • 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
      
      Thanks!
    • 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
  • Feature Request
    3 Posts | Last post August 22, 2014
    • Hello Adam,
      I made a suggestion for a change on GitHub. To use your add-in for my application I need to make a modification to the plug in so that I can run it from the console in our test environment  Issue:#115. The suggested change doesn't require the solution context to run the plugin. What do you think?
      
    • I think that's a great idea. I'll make the change soon. 
    • you are awesome thanks! Let me know if you need any other contributors. I am happy to make some of these changes for you :)
  • Crashes VS 2013 when opening a blank PS1 file - zero bytes in size
    3 Posts | Last post August 21, 2014
    • I'm experiencing a crash that takes down VS 2013.
      
      Create a new PowerShell Script Project in VS.
      Script.ps1 is created with the comments # Script.ps1 which is good.
      Right click on the project, add new item, Powershell Script.  Script1.ps1
      Click somewhere in the file that just opened.
      **Crash**
      
      Reopen VS, open the solution. Note the solution wasn't saved before the crash.  
      Right click on the project, add existing file, select Script1.ps1.
      Save the solution.
      Double click on Script1.ps1 from the Solution Explorer.
      Click somewhere in the file that just opened.
      **Crash**
      
      Open Script1.ps1 in notepad, add a # to the file.
      Save, close.
      Reopen VS, open the solution. 
      Double click on Script1.ps1, it opens fine and I can work on it.
      Add some text to Script1.ps1.
      Save it.
      Close the file.
      Double click on Script1.ps1 from the Solution Explorer. it opens fine and I can work on it.
      Remove all text from Script1.ps1.
      Save it.
      Close the file.  
      Double click on Script1.ps1 from the Solution Explorer.
      Click somewhere in the file that just opened.
      **Crash**
      
      
      Looks to be when it's zero bytes in size, the IDE crashes.
      
      
    • Wow. Easy to repro. Thanks for reporting. Hadn't seen that before. I'll look into it. 
    • Just encountered exactly the same problem. Adding some content to the file before editing it in VS helped here as well.
  • No Tests Found
    1 Posts | Last post August 20, 2014
    • I have my solution organized such that my tests are in a folder "tests" right below the module.psm1. Running Invoke-Pester from the root of my module finds all the tests. But I can't seem to get Powershell Tools for VS 2013 to recognize that I have any tests. Is there some configuration that needs to be done in order to use Pester within this solution?
  • Non-critical but annoying completion bug
    2 Posts | Last post August 19, 2014
    • Anyone else seeing this? When using tab completion in a PS file, the string that's inserted into the file is some part of what you typed, PLUS the completion matching value.
      
      Here are a couple of examples:
      
        1. If you type "Get-con" in the editor (no quotes) and select Get-Content from the completion menu, what is placed into the file is GetGet-Content.
      
        2. If you type "get-itemp" in the editor (no quotes) and select Get-ItemProperty from the completion menu, what is placed into the file is get-iGet-ItemProperty.
      
      The pattern appears to be that what is placed into the edit buffer is the first N characters you have typed + the entire matching completion string, where N is the number of characters AFTER the - that you have typed. So for the above examples:
        1. The Get is prepended because con was typed after the -.
        2. The get-i is prepended because itemp was typed after the -.
      
      So the only case that works correctly is if you type the -, and then select from the menu without entering any more characters.
    • Yuck. I don't know how that one slipped by. I'll look into it. 
  • Folders not working under PowerShell project in VS2013 Update1 and 2
    4 Posts | Last post August 13, 2014
    • Hi, I need to add folders to get some order in my PowerShell but after I added a folder to the PowerShell Project in Visual Studio 2013 if I do right-click in that folder the Visual Studio instance gets frozen and I had to close Visual Studio and start again.
      Are you going to fix this issue in the future? I'm being prevented to use this super usefull tool for this "silly" bug.
      Thanks,
      Guillermo Bas
    • I'm unable to repro this. Could you open an issue on GitHub and throw some more information about your machine\configuration on there? 
    • Hi, I have the same problem. I have another module installed (CKS Dev for Visual Studio). When Powershell and CKS dev are installed, a right-click on folder in a Powershell project frozed the Visual Studio.
      Need an update to this.
      Thanks.
    • Thanks for the info. Will have to check out the CKS Dev stuff to see what I can do. 
  • Pester TestAdapter didn't discover the tests
    2 Posts | Last post August 13, 2014
    • I am running Visual Studio 2013 Ultimate with Update2 on an x64 Win7 machine. I installed your latest visx (Version="1.0.1") and couldn't see the tests in the unit test explorer window.
      
      I disabled the strong name validation on "PowerShellTools.TestAdapter.dll" and the tests now appears in the unit test explorer window.
      
      Is there a prerequisite that I am missing?
    • I've placed Pester module in both C:\Windows\System32\WindowsPowerShell\v1.0\Modules & C:\Windows\Syswow64\WindowsPowerShell\v1.0\Modules(just to be sure) but not in  <SystemDrive>:\Users\XXXX\Documents\WindowsPowerShell\Modules\Pester.
      
      Will give that a go.
1 - 10 of 65 Items