PowerShell Tools for Visual Studio 2015

Free

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

(82) Review
Visual Studio
2015, 15
Download (383,775)
7/15/2016
3.0.399
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (82)
Q and A (183)
Sign in to write a review
Sort by:

by TeoJ | July 09 2016

Very nice! How do I enable formatting for powershell tools?

by Warren in Canada | June 06 2016

Fantastic tool. Because of the $dte variable which is bound to the IDE's live environment, the uses of this are virtually unlimited.

by mreinsmith | May 28 2016

Great tools, Thank You for providing them!

by Wilhelm.Medetz | May 18 2016

by yukiusagi2052 | April 11 2016

I appreciate for you and your software.

by BrandonStiff | March 04 2016

Great addition to VS2015! VS is one of the most full-featured and powerful IDEs out there, and a favorite of mine for years. With this add-on, I now use VS2015 for all of my PowerShell development.

by Ed Marsden | February 10 2016

by RabidTommy | February 10 2016

I like what is trying to be achieved with this extension. Just some notes to improve on, I'll definitely rate higher if they get fixed!

The Powershell Interactive Window, any chance of styling this similar to the other default Powershell prompts out-of-the-box?

Output explicitly written to the Powershell Interactive Window host for visual feedback doesn't appear to obey things like -ForegroundColor etc.

I think it needs an equivalent of $psISE? At the moment, have to evaluate something like ($ExecutionContext.Host.Name -like "PowerShell Tools for Visual Studio Host").

Good work!

by Jean-Robert Jean-Simon | February 06 2016

Great tool !
It should be included in Visual Studio natively.

by Cyril Zhou | January 19 2016

by dekeli_10 | January 17 2016

Missing crucial quality:
Missing article about how to disable this
Causing VS 2015 to hang

Bad, very bad

Prevent VS 2015 from attaching to other code
get popup: ---------------------------
Missing Dependency
---------------------------
PowerShell Tools for Visual Studio requires at least Windows Management Framework v3, which you do not have installed.



Would you like to download now?
---------------------------
Yes No
---------------------------


clicking Yes points to .net 4.0 page, which is already installed by VS 2015

after that devenv is completely stuck and needs to be killed

by Harry Solsem | January 05 2016

This extension creates an exeption upon startup of VS2015 on my system. The following are taken from activitylog.xml

<description>SetSite failed for package [PowerShellToolsPackage][Could not load type &apos;PowerShellTools.Contracts.IPowerShellHostClientService&apos; from assembly &apos;PowerShellTools.Contracts, Version=1.0.0.0, Culture=neutral, PublicKeyToken=32cd18849a3a99f8&apos;.]:{ at PowerShellTools.PowerShellToolsPackage.Initialize()&#x000D;&#x000A; at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)}</description>

by Anton Masyan | December 18 2015

by Karasev Pavel | December 01 2015

Очень удобно работать со скриптами на PS. Спасибо!

by casperln | October 28 2015

good work, a few comments

ctrl-c to copy is non-functional in the powershell interactive window

msbuild integration is non-functional

by anonmous | October 23 2015

Although I appreciate that it must have taken a lot of time and effort to put together this tool, and that it must have functionality that is useful for many people, it is hard to recommend a tool that doesn't work with include files and for which there is no response to questions about said functionality.

by Mark.Orlassino | October 18 2015

Thank you!

by Ruud Borst | October 14 2015

Finally!

by DAngeline | October 07 2015

Glad to see this actually happened Adam. Nice job!! Congratulations

by Hernan Veiras | September 09 2015

Great tool! please add support for formatting (CTRL + K + D)

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


  • Unable to install update 3.0.399
    2 Posts | Last post Tue 9:36 PM
    • No matter how I try, I can't get this update to install. I close Visual Studio, I reboot, nothing helps.
      
      Install Error : System.IO.IOException: The process cannot access the file because it is being used by another process.
    • Re-Boot your machine in safe mode and try to re-install. TIt should work 
  • Is there any way to debug scripts designed to run as part of Build processes?
    1 Posts | Last post July 21, 2016
    • Does anyone have suggestions for debugging scripts which are designed for use as part of an automated Build process? The problem is that without the incoming variables defined (and in some cases, without the objects available to act on) it would be tough to do any debugging.
      
      Two lines of thought I had (probably useless, so please just suggest what DOES work for you):
      
      1) I'm thinking that you could test $Host.Name at the start of a function, and if it is "PowerShell Tools for Visual Studio Host" then you could pre-populate some variables, but that could also get a bit clumsy and would be limited in functionality.
      
      2) Alternatively, if there were any way to alter a Build Definition so that it launched a PowerShell script under the interactive control of VS/PoSh Tools, that would be great... except that I would be very surprised if that would work. If you remember VB6, you could run the source for a .dll in a separate session of VBIDE and intercept/debug it when it was called from another task, but I don't know that anything like that could be done here.
  • Is there a window to show all Variables?
    2 Posts | Last post July 21, 2016
    • Not sure if I did not find it or it's not available. Is it possible to see all powershell variables (both built-in and the ones you created during script run) in some windows (like other editors do).
    • Yes, the Locals window (Debug >> Windows >> Locals). Unfortunately, there are dozens of build-in variables & objects, and your own variables are sorted in between them alphabetically, and excluding the "$". So $Test1 appears under T, between "StackTrace" and "true".
  • Intellisense not working on new install?
    1 Posts | Last post July 14, 2016
    • I just installed and moved over some stuff I'd been working on under ISI.  Intellisense is not working, not even as well as ISI.  Suggestions?
  • Executing script from Solution Folder with right click
    2 Posts | Last post July 02, 2016
    • I have VS 2015 solution with a powershell script in a solution folder (not in a project) and right clicking it gives the context menu with "Execute as Script" and "Execute as Script with Parameters". However, selecting either one to execute the script doesn't appear to actually do anything, i.e. there is nothing in the output window.
      
      Is this supported?
      
      Thanks,
      
      Jim
    • Hi,
      
      I have the same problem. Is debugging a PS script with arguments from with VS2015 supported?
      
      Kevin
  • Visual Studio Community Edition
    2 Posts | Last post June 02, 2016
    • Is this tool full woking at the Visual Studio Community Edition? I try to debug powershell code but it do not work? Whats wrong?
      
      Regards, SM
    • Hi Steffen,
      
      Did you tried the extension Powershell tools for Visual studio.
      
      https://visualstudiogallery.msdn.microsoft.com/c9eb3ba8-0c59-4944-9a62-6eee37294597
       
  • Insert Snippet Not Functioning Correctly
    1 Posts | Last post May 12, 2016
    • Hello!
      
      I love the PowerShell Tools for VS 2015. Thanks so much for creating this!!
      
      I'm having problems inserting snippets. They are just getting cut off. I hit CTRL+K, CTRL+X, select the snippet, and hit enter, and I get the following:
      
      #REGION Actual-Inserted-Snippet
      function CmdletName
      {
      	[CmdletBinding(
      		ConfirmImpact = "Low"
      	)]
      
      	Param
      	(
      		[Parameter()]
      		[ValidateNotNullOrEmpty()]
      		[ObjectType]
      		# ParamDescription
      		$ParameterName
      #ENDREGION Actual-Inserted-Snippet
      
      What should be inserted:
      
      #REGION Expected-Inserted-Snippet
      function $CmdletName$
      {
      	[CmdletBinding(
      		ConfirmImpact = "Low"
      	)]
      
      	Param
      	(
      		[Parameter()]
      		[ValidateNotNullOrEmpty()]
      		[$ObjectType$]
      		# $ParamDescription$
      		$$ParameterName$
      	)
      
      	PROCESS
      	{
      	
      	}
      }
      #ENDREGION Expected-Inserted-Snippet
      
      I can't include the contents of the .snippet file because I go past my maximum character limit. :(
      
      Why broken? Much Halp?
  • Broken(?) in VS2015 community
    1 Posts | Last post May 03, 2016
    • Q on SO here: http://stackoverflow.com/questions/37013169/posh-tools-for-vs-cannot-debug-scripts-modules-in-visual-studio
      
      This extension doesn't seem to work in VS2015 community. Trying to debug anything causes the script to 'build', trying to debug a single script opens it in the ISE.
      
      What causes this and how do I fix it?
  • Executing scripts remotely
    1 Posts | Last post April 22, 2016
    • Due to the way my environment is set up it is very difficult to test/debug from my desktop as my logged-in account is in a different domain from my development servers.  not sure if this is possible or not but I am looking for a way to be able to hit start in VS and have the script copied to a remote server and run from there under a different user account.  Tried to enter a session and run my code but I get an error stating "Local Script [SCRIPTPATH] cannot be run through remote powershell session".  Is there any way to achieve what I am looking for or do I need to come up with a different workflow?
  • Missing Dependency
    1 Posts | Last post April 14, 2016
    • I am getting the error 
      
      "Powershell tools for VS requires at least Windows Management Framework v3, which you do not have installed."
      
      funny thing is no matter how many times i install WMF v3+ i still get this error. but it only started giving me the error on 4/11/16. I have tried everything repair/uninstall/reinstall 
      
      Powershell works find just not in VS...
      
1 - 10 of 183 Items