PowerShell Tools for Visual Studio 2015

Free

A set of tools for developing and debugging PowerShell scripts and modules in Visual Studio.

(59) Review
Visual Studio
2015
Download (198,377)
6/29/2015
3.0.152
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (59)
Q and A (129)
Sign in to write a review
Sort by:

by Kjetil Tonstad | June 24 2015

Very useful

by Ken Cenerelli | May 28 2015

Love the functionality!

by ti831 | May 12 2015

by Igor Abade V. Leite | May 11 2015

Love it! I'm using PoshTools to build my TFS administration module (http://github.com/igoravl/tfscmdlets).

Writing PowerShell code inside Visual Studio with PoshTools is a breeze - in fact, it's quite enjoyable! :-)

by Alexander Romanov | April 20 2015

by aL3891 | April 20 2015

Really great stuff!
How far off do you think dsc resource class support is?
that and being able to build a module so that it's deployed
into the module path would be really cool!

Adam R Driscoll April 21 2015
| Edit |
Delete

Can you describe what you're looking for in DSC support? With the recent addition of x64 support, DSC should work.

As for the deployment of a module, I agree. That would be a great feature. Please feel free to throw some Issues up on GitHub about either of these.

by Roy Mayfield | April 04 2015

The Bomb. Solved Source Control Hell. Epicness.
'nuff said ;)

by eliassal | March 30 2015

Hi,
Great tool
I downloaded, setup the tools and fired VS 2013 premium, created a script project but I am not getting the Intellisense
I have WMF 5 Feb preview on win 8.1 box
Should it work correctly or not because of WMF 5?
Thanks in advance

Adam R Driscoll April 02 2015
| Edit |
Delete

Hey there. You might want to try the latest dev build. aka.ms/Get-PoshTools

by albertcp | March 03 2015

by Yatajga | February 20 2015

by Kaushik N. Patel | February 17 2015

Nice PowerShell extension. It will be great if can also add support for PowerShell DSC.

Adam R Driscoll February 18 2015
| Edit |
Delete

We are working on x64 and DSC support right now. You can find our pre-release builds here: https://ci.appveyor.com/project/PoshTools-MSFT/poshtools/branch/dev

by twolfmain | February 04 2015

by Leopold Lerch | December 17 2014

Only minus is the lack of Support of x64 modules (like the SharePoint-dlls). In any other aspect it deserves 5 stars

by wikky2007 | December 05 2014

by Steve Rathbone | October 04 2014

by Michael J. Prentice | October 03 2014

Love it, thank you!

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.

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


  • Script for Visual Studio NuGet PowerShell
    1 Posts | Last post June 27, 2015
    • How can I include references to Visual Studio NuGet PowerShell to be able to use IntelliSense in a script for Visual Studio NuGet PowerShell?
  • Comment commands
    1 Posts | Last post June 27, 2015
    • Why comment commands does not work when I open ps1 file?
      
      I mean neither Ctrl+E, Ctrl+C or Ctrl+E, Ctrl+U nor toolbar buttons on the Text Editor toolbar. They just are not active!
  • Intellisense
    2 Posts | Last post June 26, 2015
    • Will this allow for intellisense to work with other plugins?  For example - PowerCLI for VMware systems - how would I add that into VS and have intellisense populate when I put in PCLI commands? 
    • This should work with any PowerShell module. 
  • Won't initialize in VS2015
    4 Posts | Last post June 24, 2015
    • Running VS 2015 Community edition on Win 7 Enterprise. The PoshTool add-on fails to initialize with following message. 
      
      "PowerShell host initializing has not yet completed, please try again later." 
      
      I experienced the same error on VS 2013 Community edition as well. 
      
      Suggestions?
      
    • Can you try updating to the latest and see if you experience this issue? Please make sure to uninstall your existing extension before installing the new one. 
    • Adam,
      
      Same error. I removed the old version of the extension and made a fresh install of 3.0.152. No dice. What's your next suggestion?
    • Could you please open an issue on GitHub? It'll get more attention from the Microsoft team. 
      
      https://github.com/adamdriscoll/poshtools/issues
      
      We have seen issues where execution policy prevents the host from starting up properly. What is your x64\x86 policy set to? 
  • Won't initialize in VS2013
    2 Posts | Last post June 22, 2015
    • Any ideas?  Tried uninstall and reinstalling.
      
      https://www.dropbox.com/s/i5mfyskdyc70hb2/vs2013.png?dl=0
    • Can you try updating to the latest and see if you experience this issue? Please make sure to uninstall your existing extension before installing the new one. 
  • Minor issues
    2 Posts | Last post June 16, 2015
    • Just trying this out... this is a great addition to VS. Thanks for it. Two things I noticed:
      
      1) The Enter key seems to invoke some kind of autocomplete when it's not always appropriate, e.g. if I just type "d:" and hit enter, it adds the path of the first alphabetic folder on D. It's kind of awkward to just change drives, I have to use shift-enter followed by enter
      
      2) What color profile properties are used? The colors are pretty unreadable -- I assume this has to do with my own Visual Studio scheme, but I'm not sure what I need to change to alter the colors used by the shell.
    • 1. We've done some work around IntelliSense lately. Can you give the latest dev bits a try? https://ci.appveyor.com/project/PoshTools-MSFT/poshtools/branch/dev We should be releasing an update shortly. 
      
      2. If you go into Tools->Options->Fonts and Colors, you will see options for PowerShell. 
  • Failed to initialize on new install of VS 2015 RC
    7 Posts | Last post June 09, 2015
    • When starting VS 2015 RC window with title "PowerShell Tools for Visual Studio Error", and a label with the text
      
      "Failed to initialize PowerShell Tools for Visual Studio.System.Reflection.TargetINvocationException: Exception has been thrown by the target of an invocation. --->
      Micarosoft.VisualStudio.COmposition.CompositionFailedException: Expected 1 export(1) with contract name "PowerShellTools.VisualStudioEvents" but found 0 after applying applicable constraints.
      
       at
      Microsoft.VisualStudio.Composition.ExportProvider.GetExports(ImportDefinition importDefinition)
       at
      ... (snip) ...
       at Microsoft.VisualStudio.ComponentModelHost.ComponentModel.GetService[T]()
       at PowerSHellTools.Diagnostics.DiagnosticsDialogPage..ctor()
       -- End of inner exception stack trace --
       at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       ... (snip) ...
       at Microsoft.VisualStudio.Shell.Package.GetDialogPage(Type dialogPageType)
       at PowerShellTools.PowerShellToolsPackage.InitializeInternal()
       at PowerShellTools.PowerShellToolsPageage.Initialize()
      
      is shown. VS starts after clicking OK on this dialog.
    • Hi Martijn,
      
      What version of Windows are you running? 
    • I get this error when Debugging a vsix in the experimental mode with VS2015 RC on Windows 10 Insider preview build 10122.
    • I get a similar error when starting VS2015RC on W10P10122.
      "Failed to initialize PowerShell Tools for Visual StudioSystem.InvalidOperationException: Collection type must derive from ICollection<T>" ...
      
      
    • I should probably add that I first received this error yesterday. But haven't been using VS much lately.
    • I have the same error. Got it when I switched from VS 2015 Update 4 to VS 2015 Enterprise RC.
    • Can you try the latest dev build to see if it resolves your issue? 
      
      http://aka.ms/get-poshtoolsNightly
  • pssproj is not supported by this version
    8 Posts | Last post June 08, 2015
    • very excited to finally use a proper IDE for powershell, just downloaded ps tools and installed on windows 7 x64, with VS 2013 SP4 and now getting an error whenever I attempt to create a new PS project.
      
      VS complains pssproj type is not supported by this version of the application. Any ideas what I'm doing wrong? I've selected all .net versions from the drop down box but that hasn't done me any good.
    • I have the same problem on Win8 and VS2013Community version. Is the community version supported?
    • Furthermore, the version that was installed on my machine is 1.2.3.4 and even if i do an update from VS it tells me that "The extension is already installed to all applicable products.". (I haven't restarted the machine yet.)
    • I have the same issue here.
      
      Windows 8.1 Enterprise 
      VS 2013 Community Edition Update 4
      
      
    • Can you guys download again? There was an issue with the VSIX that was uploaded to the Gallery. 
    • Now it works. Awesome man! fastest response to an incident ever ;)
      
    • yep can confirm it also works for me! many thanks
      
      now is there a chance you can put a GUI creator so I can design forms for the people who prefer those? :)
    • Working on it ;) https://www.youtube.com/watch?v=418sH2lcZ1w
  • How can I use Code Snippets in that project?
    1 Posts | Last post June 07, 2015
  • How do I place the script files on the build output?
    4 Posts | Last post June 04, 2015
    • I need the script files that are on the project to be copied to my build drop folder. I created a PowerShell Script Project and I see that it does not even have a 'Build' option, so I can't use something like post build scripts.
      
      Is there a way to make the project "Buildable" and then put the script files in the output folder?
    • I'll have to see why Build isn't available. Could you please enter a GitHub issue for this? 
    • Hi.
      Any news on this one?
      I want to use the scripts as deploy scripts for my lab so I realy want them in my output.
    • @Jens - No progress on this one. There is Issue #94 (https://github.com/adamdriscoll/poshtools/issues/94) that is kind of related. Deploying scripts sounds like a pretty important feature. 
1 - 10 of 129 Items