PowerShell Tools for Visual Studio 2015

Free

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

(80) Review
Visual Studio
2015
Download (361,935)
3/29/2016
3.0.375
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (80)
Q and A (179)
Sign in to write a review
Sort by:

by mreinsmith | Sat 11:54 AM

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)

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!

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


  • Visual Studio Community Edition
    1 Posts | Last post May 17, 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
  • 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...
      
  • referencing custom functions and intellisense
    1 Posts | Last post April 13, 2016
    • I have a ps1 file that contains a number of functions used regularly.  Is there a way to load this file so that intellisense and tab completion will work with these functions?
  • Failed to load Pester module
    1 Posts | Last post April 12, 2016
    • I create a tests.ps1 files inside my Powershell project in VS2015. the test explorer recognizes the declared test, but when I try to run the test I get this: "Result Message:	Failed to load Pester module. The specified module 'Pester' was not loaded because no valid module file was found in any module directory."
      
      I discover that I did not have the Pester in my Pc, I download it from GitHub, then I add the folder to the $env:PSModulePath. Powershell identifies the module, but was not able to import it, so I move the folder from its original location to:
      c:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\
      Now any console of powershell is able to import the module: ISE, Powershell console, Powershell interactive window in VS2015.
      
      Then I try to run the test again, I keep getting the same message.
      
      I follow thw instructions in this same page of someone that face the same, but its answer does not apply to me due I do not have any .package file for nugget.
  • PS1 Editor Theme Colors Are Too Dark to Read
    1 Posts | Last post March 31, 2016
    • If I change Visual Studio color theme to something dark, the PS1 editor uses syntax highlighting colors that are unreadably dark. Is that because of this extension, or are the bad PS1 colors built into Visual Studio's default color themes? How can I switch to better default colors without tediously editing multiple items in each theme?
  • SignatureDescription Error while installing
    1 Posts | Last post March 23, 2016
    • I get an error while trying to install this in Visual Studio Premium 2013.
      
      23/03/2016 11:50:18 - System.Security.Cryptography.CryptographicException: SignatureDescription could not be created for the signature algorithm supplied.
         at System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo(AsymmetricAlgorithm key)
         at System.Security.Cryptography.Xml.SignedXml.CheckSignature(AsymmetricAlgorithm key)
      
      Is it compatibility issue? Or do I have to apply any update?
      
  • Start in solution directory
    2 Posts | Last post March 14, 2016
    • Is there a way to make the PowerShell Interactive window start in the same directory as the solution file? This seems like a good default behaviour.
    • If you execute: ii $profile
      You'll get the path to your profile for PoshTools. Create the file it is looking for, and in that file, add: 
      if($dte.Solution -ne $null)
      {
          $slnDir = [System.IO.Path]::GetDirectoryName($dte.Solution.FileName)
          Push-Location $slnDir
      }
      
1 - 10 of 179 Items