PowerShell Tools for Visual Studio 2013

Free

PowerShell integration for Visual Studio

(54) Review
Visual Studio
2015, 2013
Download (134,203)
4/16/2015
1.0.5
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (54)
Q and A (107)
Sign in to write a review
Sort by:

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.

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.

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


  • Error loading the tool
    10 Posts | Last post Wed 4:58 PM
    • I have just installed it to my VS2013, I closed VS and launched it again. But I got
      
      Failed to initialize PowerShell Tools for Visual Studio.System.IO.FileNotFoundException: Could not load file or assembly 'System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
      
      File name: 'System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
      
         at PowerShellTools.PowerShellToolsPackage.InitializeInternal()
      
         at PowerShellTools.PowerShellToolsPackage.Initialize()
      
      
      
      WRN: Assembly binding logging is turned OFF.
      
      To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
      
      Note: There is some performance penalty associated with assembly bind failure logging.
      
      To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    • After I installed Windows Management Framework 4.0 and launch my VS2013 again, I got another error message.
      
      Failed to initialize PowerShell Tools for Visual Studio.System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Composition.ImportCardinalityMismatchException: No exports were found that match the constraint: 
      	ContractName	PowerShellTools.VisualStudioEvents
      	RequiredTypeIdentity	PowerShellTools.VisualStudioEvents
      
         at System.ComponentModel.Composition.Hosting.ExportProvider.GetExports(ImportDefinition definition, AtomicComposition atomicComposition)
      
         at System.ComponentModel.Composition.Hosting.ExportProvider.GetExportsCore(Type type, Type metadataViewType, String contractName, ImportCardinality cardinality)
      
         at System.ComponentModel.Composition.Hosting.ExportProvider.GetExportedValueCore[T](String contractName, ImportCardinality cardinality)
      
         at System.ComponentModel.Composition.Hosting.ExportProvider.GetExportedValue[T](String contractName)
      
         at System.ComponentModel.Composition.Hosting.ExportProvider.GetExportedValue[T]()
      
         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)
      
         at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
      
         at Microsoft.VisualStudio.Shell.Package.GetDialogPage(Type dialogPageType)
      
         at PowerShellTools.PowerShellToolsPackage.InitializeInternal()
      
         at PowerShellTools.PowerShellToolsPackage.Initialize()
    • I am getting the same error, loaded find the first time but subsequent startups produce the error.
    • Not sure if this will work for you but I had a similar error and resolved it by installing the PowerShell ISE Add-On for VS2013 Extension.
    • Can you guys try the latest dev version to see if this resolves your issue? 
      
      https://ci.appveyor.com/project/PoshTools-MSFT/poshtools/branch/dev/artifacts
    • @J_Young_80 - Same series of issues (Automation -> ImportCardinalityMismatchException) seems to be solved via Powershell ISE addon.
    • Weird. We need to look into this. The extension is no way related to this one. 
    • I can confirm WernerCD's findings. This was with Windows 7 x64.
    • I had the same problem until I uninstalled the addin and reinstalled it. I think the problem is that Powershell v4 must be installed before you install this package. I'm up and running with it. Only problem I'm having now is that it will not stop at breakpoints.
    • @SMorley - trying installing the latest build from the link Adam posted above, the breakpoint "skipping" should be fixed...
  • Getting Started?
    2 Posts | Last post Sun 4:43 PM
    • I've read what I can find on the Github Wiki and here, but am having a rough time getting started with the extension.  A few (hopefully simple) questions:
      
      * Where is the latest "Getting Started' documentation?  Is it the GitHub wiki (which seems out of date)?
      * Is one module project intended to represent a single module or can it be a module library?
      * Is there any project build support to perform things like .zipping up modules, or publish support?
      
      Given the good reviews and comments I'm reading below, I must be doing something terribly wrong.. :)
    • - The GitHub wiki is the latest. There really isn't a good "Getting Started" page. I can certainly work on adding one. If you have any specific questions, let me know and I'll make to include them in the wiki. 
      - Really, the project templates are pretty much all the same. I hope to extend this but as it stands the only difference is the default items. 
      - Nope, not currently any zipping or publish support. 
      
      Would love to see some GitHub items outlining what you are looking for. :)
  • Need to type extra space after Intellisense
    3 Posts | Last post April 09, 2015
    • Just installed and I'm seeing annoying behavior.
      
      Example: I type "Write-Host" (no tab completion). After typing "Write-Host" I need to hit space twice for "Write-Host" to become "Write-Host ".
    • Can you try one of our new dev builds? This may be fixed: http://aka.ms/Get-PoshTools. 
    • I just tried one of the newer dev builds and this appears to be fixed. Thanks for the follow-up!
  • Will not install
    5 Posts | Last post April 03, 2015
    • On a fresh installed computer, With VS2013.4 and vs2015CTP, it says that I am mission a .Net Framework. However, it will not say witch one. 
      
      Any ideas?
      
      20.01.2015 13:31:39 - The following target products have been selected...
      20.01.2015 13:31:39 - 	Microsoft Visual Studio Ultimate 2013
      20.01.2015 13:31:39 - 	Microsoft Visual Studio Ultimate 2015 CTP
      20.01.2015 13:31:39 - 
      20.01.2015 13:31:39 - Beginning to install extension to Microsoft Visual Studio Ultimate 2013...
      20.01.2015 13:31:39 - Install Error : Microsoft.VisualStudio.ExtensionManager.MissingTargetFrameworkException: The extension 'PowerShell Tools for Visual Studio 2013' requires a version of the .NET Framework that is not installed.
         at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.CheckForValidDotNetFramework(IExtension extension)
         at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.CheckForInstallBlockers(InstallableExtensionImpl extension, IInstalledExtensionList modifiedInstalledExtensionsList, Boolean isNestedExtension, Boolean& olderVersionInstalled)
         at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallInternal(InstallableExtensionImpl extension, Boolean perMachine, Boolean isNestedExtension, IDictionary`2 extensionsInstalledSoFar, List`1 extensionsUninstalledSoFar, IInstalledExtensionList modifiedInstalledExtensionsList, AsyncOperation asyncOp, UInt64 totalBytesToWrite, UInt64& totalBytesWritten)
         at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.BeginInstall(IInstallableExtension installableExtension, Boolean perMachine, AsyncOperation asyncOp)
         at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallWorker(IInstallableExtension extension, Boolean perMachine, AsyncOperation asyncOp)
      
    • What OS?  If it's Windows 8, .NET 4.0 is installed by default.  Could try installing .NET 3.5 via "Programs and Features" -> "Turn Windows features on or off".
    • Hello. I have the same trouble with VS 2013.4 and VS 2015CTP installed. Some extensions fails to install with the same message "the extension ... for visual studio  2013 requires a version of the .Net framework that is not installed". I think, this is somehow related with incorrectly installed .net framewok 4.5. I had to uninstall VS2015 and 2013, and then uninstall all .net frameworks version 4 (4.5, 4.5.1, 4.5.2, 4.6RC). Afterwards I install VS2013.4, and problem was fixed.
    • Windows 8.1 - Fully patched
      .Net Framework 3.5 and .Net framework 4.5 Advanced Features installed
      Getting the same error on VS2013.4 and VS2015CTP. 
      
      I read Bibliarij workaround with interesst, however since this exteionsion is not critical to me, I can wait until you have som suggestions and try them instead of uninstalling VS2015.. 
    • I had the same issue on my Windows 8.1 PC with VS2013.4 and VS2015CTP installed.  What fixed the issue for me was uninstalling VS2015CTP and doing a "repair" install of Windows 8.1.  I'm not sure if the removal of VS2015CTP was necessary, but the repair install of Windows 8.1 was as nothing else I tried worked.
  • Profile in Debug Interactive window?
    2 Posts | Last post March 24, 2015
    • Hi, I can't find mention or figure out how to load my PowerShell profile (as in $profile) in to the Debug Interactive window. Is it possible?
    • Hi Daniel, 
      
      PoshTools actually uses it's own profile. Same location, just named: PoshTools_profile.ps1
      
      You could just load your existing profile in that script or move whatever you need in there. 
  • Debug with break point fails?
    2 Posts | Last post March 24, 2015
    • Hi,
      
      When I place a break point on a line and I start with F5, I get the following results:
      
      [ERROR] C:\Users\xxxxx\documents\visual studio 2013\Projects\PowerShell Script Project1\PowerShell Script Project1\Script.ps1 : Could not load type 'System.Management.Automation.DebuggerCommandResults' f
      [ERROR] rom assembly 'System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
      [ERROR] At line:1 char:1
      [ERROR] + . 'C:\Users\xxxxx\documents\visual studio 2013\Projects\PowerShell Script Pr ...
      [ERROR] + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      [ERROR]     + CategoryInfo          : NotSpecified: (:) [Script.ps1], TypeLoadException
      [ERROR]     + FullyQualifiedErrorId : System.TypeLoadException,Script.ps1
      [ERROR]  
      
      Any ideas?
      Thanks
    • Do you have PowerShell v3 installed (Windows Management Framework v3)?
  • Using powershell 32 bit
    2 Posts | Last post March 18, 2015
    • I'm using VS2013 community edition and have installed the "dog food" version of the tools, as I am having troubles with debugging and break points. When I debug a script and check the environment
      
      [environment]::Is64BitProcess the result is "true"
      
      How do I set the environment to be 32bit when debugging? 
      (when I used the previous Poshtools it was 32 bit)
    • Hey Mark,
      
      Could you log and issue on GitHub. There currently isn't a way to run 32-bit on a 64-bit machine. It always runs 64-bit. 
  • Visual Studio Community Edition
    4 Posts | Last post March 18, 2015
    • Hello,
      
      I suppose it's not compatible yet with the Community edition? Is that planned?
      
      For now I get this error message when VS starts and this module is installed (I tried to re-install it to make sure, but the same error comes back):
      
      "Failed to initialize PowerShell Tools for Visual
      Studio.System.IO.FileNotFoundException: Could not load file or assembly 'System.Management.Automation, Version=3.0.0.0 [...]"
      
      Unfortunately I can't put the screenshot here, so it's hosted at this URL:
      http://s12.postimg.org/kkwidv1el/Clipboard01.jpg
      
      Visual Studio Community 2013
      Version 12.0.31101.00 Update 4.
    • It works with community. You need to install Windows Management Framework v3. 
    • Hi,
      I use community edition and Windows 7 sp1. And Management Framework 4. But I get this error message: The extension 'Powershell tools for visual studio 2013' requires a version of the .NET Framework that is not installed'..
      
      I have framework 4.5. It says nothing in the logs about what version is missing. You have any idea what Framework version I'm missing?
    • This is an issue we fixed in newer versions. Want to try a dev build? https://ci.appveyor.com/project/PoshTools-MSFT/poshtools/branch/dev/artifacts
  • Install Question
    2 Posts | Last post March 18, 2015
    • I tried to install this today and got this error:
      
      3/17/2015 9:44:02 AM - Searching for applicable products...
      3/17/2015 9:44:02 AM - Found installed product - Microsoft Visual Studio Express 2013 for Windows Desktop
      3/17/2015 9:44:02 AM - Found installed product - Global Location
      3/17/2015 9:44:02 AM - 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()
      
      Is Microsoft Visual Studio Express 2013 for Windows Desktop not supported?
    • Hi, Express isn't supported but Community edition is. https://www.visualstudio.com/en-us/news/vs2013-community-vs.aspx
  • debugging not working properly on my visual studio 2013
    3 Posts | Last post March 02, 2015
    • I installed PowerShell Tools for Visual Studio 2013 (Powershell version 4). I created a powerShell Script Project and I can only debug the script code if the project was opened at the first time. The farther debugging will never hit the breakpoint. I have to restart vs 2013 to get debugging work only one time. Please help me out, thanks.
    • This is a known issue. Try giving our pre-release build a shot. Should be fixed. 
      
      https://github.com/Microsoft/poshtools/releases/tag/Dogfood-2-27-14
      
    • This fixed my debugging issue. Thank you very much.
1 - 10 of 107 Items