PowerShell Tools for Visual Studio


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

(58) Review
Visual Studio
2015, 2013
Download (170,145)
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Reviews (58)
Q and A (121)
Sign in to write a review
Sort by:

by Ken Cenerelli | Thu 6:15 PM

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 |

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

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 |

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 |

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.

by Plinio B. Figueiredo | September 02 2014

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

  • Download link points to the wrong extension!!
    2 Posts | Last post Fri 5:37 PM
    • Wow.  Both the download link on the web, and the extensions and updates tool in Visual Studio 2013 both install the File Path on Footer extension.
      How would those wires get crossed?
    • I noticed the same thing. I've spent the last 20 minutes trying to figure out why Powershell tools wasn't updating and finally discovered that it is installing the File Path Footer extension instead.
  • VS craches when i right click on folders
    4 Posts | Last post Fri 5:02 PM
    • I have a Script project created with the PowerShell Project Template.
      I can create a folder, but i am unable to right click on the folder and add new items. 
      When i right click on a folder my Visual Studio just craches.
      My current workaround is to unload the project and edit the .pssproj file. Am i the only one experiencing this problem? Anyway i can solve it?
    • I know others have seen this in the past and I thought it had been fixed. There was also an error when some other extension was installed (I can't remember which now). If you could get a crash dump, that would be very helpful. 
    • I to have this exact same issue.. unfurtunately it never crashes at all, so I have no idea why this is happening...
    • I can confirm I also have this issue :-(
      VS Professional 2013
      v12.0.40121.00 Update 5 CTP
      PowerShell Tools 1.3
  • Failed to initialize on new install of VS 2015 RC
    5 Posts | Last post Fri 9:45 AM
    • 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.
      Microsoft.VisualStudio.Composition.ExportProvider.GetExports(ImportDefinition importDefinition)
      ... (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.
  • Windows 8.1 Host unable to Enter-PSSession to VMs
    8 Posts | Last post May 16, 2015
    • On Windows 8.1 Host using Visual Studio 2013 Ultimate Update 4 to Windows Server 2012, unable to Enter-PSSession to VM target machines with the following error:
      PS C:\WINDOWS\system32> Enter-PSSession -ComputerName <computer>
      [ERROR] Enter-PSSession : Connecting to remote server <computer> failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x80090311 occurred while 
      [ERROR] using Kerberos authentication: There are currently no logon servers available to service the logon request.  
      [SNIP]  Possible causes are:
      Also fails from the target machine to the Host. Works fine between VM to other windows server 2012 VMs on the domain. Works fine to the VM machine from a physical Windows 8.0 machine on the domain. Have checked and re-checked trusted hosts, firewall, SPN configuration. VS hangs when using "Enter Powershell Sesson" using icon.
    • Windows 8.1 machine is a Dell Precision M6700 i7 updated from Windows 8.
      Loving this product!
      Thanks again.
    • This sounds like it could be a networking issue. Does the same command work in PowerShell.exe? VS shouldn't hang though. That sounds like a bug. It'd be great if you could open an issue on GitHub so we can track it. 
    • Thanks for getting back to me, Adam.
      The problem is on my end. Noticed today that the command line prompt defaults to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE" instead of "..Visual Studio 12.0\Common7..." in the REPL window as on my other machines. Apparently this is a side-by-side issue from long ago when I removed VS 2012 and installed VS 2013. The VSIX is installing PowerShell Tools in the correct folder. Can you suggest a way to configure this properly by hand without uninstalling VS 2013?
    • Noticed from "Get-PSSessionConfiguration" that the working instances are running PSVersion 3.0 and the affected machine is running 4.0. In response to your earlier question, PowerShell ISE and Windows Powershell are both working fine(PSVersion 3.0 snd 4.0 respectively).
    • Ok. If there is a difference between the ISE, then we certainly have a problem. A couple things that I would suggest. 
      Turn on some logging for PoshTools: https://github.com/adamdriscoll/poshtools/wiki/Debugging-PowerShell-Tools-for-Visual-Studio
      Open an issue on GitHub and provide the log contents around the time you when to try and connect to the remote machine. 
      The Microsoft guys should be able to help more with this one as they helped to implement all the remoting support. 
    • Thank you so much, Adam. Will open an issue on GitHub.
    • Did not need to reinstall anything; Got PoshTools remoting to work in my Windows 8.1 configuration by rebuilding Visual Studio item and template caches.
  • PowerShell Tools for VS2013 Windows Desktop Express
    2 Posts | Last post May 09, 2015
    • Hi, Is PowerShell extension supporting Visual Studio 2013 For Windows Desktop Express ?
      At present, I'm getting the following error when installing it :
      05/05/2015 16:40:31 - 	Version         : 3.0.1002
      05/05/2015 16:40:31 - 	Description     : A set of tools for developing and debugging PowerShell scripts and modules in Visual Studio.
      05/05/2015 16:40:31 - 	Locale          : en-US
      05/05/2015 16:40:31 - 	MoreInfoURL     : http://adamdriscoll.github.io/poshtools
      05/05/2015 16:40:31 - 	InstalledByMSI  : False
      05/05/2015 16:40:31 - 	SupportedFrameworkVersionRange : [4.5,)
      05/05/2015 16:40:31 - 	Supported Products : 
      05/05/2015 16:40:31 - 		Microsoft.VisualStudio.IntegratedShell
      05/05/2015 16:40:31 - 			Version : [12.0]
      05/05/2015 16:40:31 - 		Microsoft.VisualStudio.IntegratedShell
      05/05/2015 16:40:31 - 			Version : [14.0]
      05/05/2015 16:40:31 - 		Microsoft.VisualStudio.Pro
      05/05/2015 16:40:31 - 			Version : [12.0]
      05/05/2015 16:40:31 - 		Microsoft.VisualStudio.Pro
      05/05/2015 16:40:31 - 			Version : [14.0]
      05/05/2015 16:40:31 - 	References      : 
      05/05/2015 16:40:31 - 		-------------------------------------------------------
      05/05/2015 16:40:31 - 		Identifier   : Microsoft.VisualStudio.MPF.11.0
      05/05/2015 16:40:31 - 		Name         : Visual Studio MPF 11.0
      05/05/2015 16:40:31 - 		Version      : [11.0]
      05/05/2015 16:40:31 - 		MoreInfoURL  : 
      05/05/2015 16:40:31 - 		Nested       : No
      05/05/2015 16:40:31 - Searching for applicable products...
      05/05/2015 16:40:31 - Found installed product - Microsoft Visual Studio Express 2013 for Windows Desktop
      05/05/2015 16:40:31 - Found installed product - Global Location
      05/05/2015 16:40:31 - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
         at VSIXInstaller.App.InitializeInstall()
         at System.Threading.Tasks.Task.InnerInvoke()
         at System.Threading.Tasks.Task.Execute()
    • The extension doesn't support express editions. It does support Community Edition if you're looking for something free. 
  • First time use - need output window
    2 Posts | Last post May 05, 2015
    • Hit you on twitter, but the first time you launch in vs2015 RC, you must open the output window manually before you can see results from scripts: ctrl-alt-o.  This was not the behavior in vs2013.  I just tested on a clean vs2013 and installed both at the same time from the installer.  
    • Weird. Sounds like a bug. Wanna throw an issue on GitHub? 
  • Automatic brace completion cannot be disabled
    2 Posts | Last post April 29, 2015
    • Visual Studio 2013 Update 4 with this installed, I cannot turn off Automatic brace completion.
      Tools -> Options -> Text Editor -> All Languages (or PowerShell) -> General
      Clear the checkbox, restart, the option is selected.
      Uninstall this extension; the option works as expected.
      Reinstall latest extension; problem returns.
    • Hey Scott,
      This is a lacking feature and known issue. If you have any comments, please add them to this issue: https://github.com/adamdriscoll/poshtools/issues/231
  • Scripts requiring v3.5
    2 Posts | Last post April 28, 2015
    • Is there anyway to use this with scripts requiring a lower version of the .net frameworks like v2.0/v3.5?
      Specifically, if you are using this to develop scripts for SharePoint 2010 ( Microsoft.Sharepoint.PowerShell), .NET 4 can't be used.
    • That's an interesting issue. We'd have to see if we could compile the PowerShell host EXE as 3.5. Not sure if that is possible. Could you open a GitHub issue so we can track it? 
  • Interactive Debugging
    2 Posts | Last post April 28, 2015
    • I would like to use this adding. Unfortunately, the project I am working on is complex and we can't just rewrite everything to use VS projects.
      Need support for invoking the debugger from the interactive PS debugger window.  When I put breakpoints into sources of modules that are currently loaded, I need the break points to stop execution that is initiated in the interactive debugger window. Powershell_ise supports this scenario. Need the same from VS for it to be useful.
    • Thanks for the feedback. Could you open an issue on GitHub so we can track it? 
  • Failed to initialize PowerShell Tools for Visual Studio
    3 Posts | Last post April 24, 2015
    • I've just installed this extension, and now I get this error message when starting up VS 2013 Update 4. I first got a warning I needed 'Management Tools' (or similar) for Windows 7, which I duly installed and restarted, now I get the error. Anyone else?
    • Hey Brady, what's the error message? 
    • I guess, any additional info besides what's in the title? 
1 - 10 of 121 Items