PowerShell Tools for Visual Studio 2015


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

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

by Sean Liming | August 23 2015

Nice to have scripting out of VS, PowerShell ISE is still a little more light weight.

by Steve Rathbone | August 05 2015

Keep going guys - this is phenomenal!

big thank you to all involved, including the pester team!

by Ilia101 | July 28 2015

Very nice ! Thanks !

by Alexandr Biryukov | July 24 2015

It is very useful, thank you!

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 |

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 Michael J. Prentice | October 03 2014

Love it, thank you!

by Christian Thoenes | September 25 2014

This is awesome! Thanks a lot!

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

  • Debug VS variable
    4 Posts | Last post Sun 2:31 AM
    • Is it possible to capture and export data from a debug C# variable into a csv file using PowerShell Interactive Windows?
    • You might be able to access that via the $DTE object that is available in the runspace. 
    • Thanks Adam.
      I was able to access DTE object. I still need to understand this object more, but did found dte.debug.... I just have to figure this out.
    • I was able to capture variable value using $dte.debugger.GetExpression("variable).value. I can not successfully get the value for complex object or DataSet.  How can i get a value from a DataSet or a custom object using GetExpression like this $dte.Debugger.GetExpression("byDataSet")?
      This PowerShell tool is the best and keep up the good work!
  • Caching off errors
    2 Posts | Last post August 28, 2015
    • Hi
      It has been working perfectly well for me but now seems like its caching errors. Tool is complaining about variables that don't exist in my power-shell solution. How can i clear the cache?
    • I have the same issue. It appears to be loading a previous version of the script even though I have made changes and saved the file. Closing the file out and reopening does not fix the issue. The only thing that seems to work is closing VS and reopening it. 
  • PowerShell Interactive Window load profile.
    1 Posts | Last post August 27, 2015
    • Hi, 
          How can I load my profile.ps1 in PowerShell Interactive Window the same model how occurs with PowerShell initialized by windows.
      Tks in advance.
  • Intellisense
    5 Posts | Last post August 25, 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. 
    • Adam,
      But how do you get the module imported into VS?  
    • Really, you shouldn't have to do anything special. We use the same mechanism as the ISE and command line to discover commands. You still don't see them after an import-module? 
    • Hi Adam,
      I have the same question/issue.  I'd like to import the PowerCLI module so intellisense works for VMware cmdlets.  I've tried adding 'Import-Module vmware.vimautomation.core' to the script itself, I've opened a PowerShell session and imported the module.  I even added it to my user startup script.  That last one finally allowed me to complete VMware cmdlets names by hitting tab.  However, it won't autocomplete parameters ... so I'm stuck writing out the whole thing manually.
      Is this something that's supported?
  • Visual Studio 2015 crashes when saving ps1 script
    1 Posts | Last post August 17, 2015
    • This situation started to appear after I updated PoSh tools to version 3.0.177.
      I open Powershell script project with several scripts. When I make changes to script and trying to save (Ctrl + S or by pressing button on toolbar) VisualStudio crashes with standard message "Visual Studio stopped working..."
      Tried to save C# file - its ok. So the problem is in this extension.
      Please fix it.
  • Shift + E bug
    5 Posts | Last post August 11, 2015
    • After installing v3.0.163, I couldn't type capital 'E' character (Shift + E) in the C# editor. I think it's a very critical bug. Some people might be mad at Visual Studio 2015 if they would not know that actually it's your plugin causes that.
    • I also got affected by this bug today
    • +1 for me. Two hours gone.
    • This also happened to me.  Found the "Shift+E, F5" chord bound to the EditorContextMenus.CodeWindow.PowerShell.ExecuteAsScript command.
      It makes typing things like "IEnumerable" unnecessarily difficult.
    • This has been resolved in the GitHub repo and we will be releasing a new version today. 
  • Failed to load Pester Module
    2 Posts | Last post July 30, 2015
    • This was working just fine for me in VS 2013 but when I installed VS 2015 RC I get the following error:
      Message: Failed to load Pester module. The specified module 'Pester' was not loaded because no valid module was found in any module directory.
      I get this error in BOTH Visual Studio 2013 and Visual Studio 2015 now. I have uninstalled the Powershell Tools and reinstalled them in both IDEs. Pester tests work fine when invoked in a standard Powershell. I only get this message in Visual Studio. 
    • I was getting this earlier today. For me the problem was that I had a custom nuget.config file which was placing downloaded packages out to a ../lib directory rather than the default ./packages. Removing this made everything work again.
  • Won't initialize in VS2015
    6 Posts | Last post July 28, 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. 
    • 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. 
      We have seen issues where execution policy prevents the host from starting up properly. What is your x64\x86 policy set to? 
    • I experienced the same issue in Visual Studio 2013 with PoshTools for VS2013.
    • Same problem here in VS2015 Enterprise. Execution policy for x86/x64 is set to unrestricted.
  • PowerShell Tools for VS2013 Windows Desktop Express
    3 Posts | Last post July 27, 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. 
    • Is there any possibility of the extension supporting Express edition in the future?
  • Can't open ps script in from Visual Studio
    1 Posts | Last post July 26, 2015
    • Hello.
      I've created Powershell script project in VS 2015, and started creating my script. Then i left VS window for some time and worked with other programs. And when i came back to VS, and wanted to type somethimg in script tab, VS hanged, and dialog about "Visual studio is waiting for the end of operation" was shown. Reopening VS does not help. I can no more work with powershell script.
1 - 10 of 136 Items