PowerShell Tools for Visual Studio 2013

Free

PowerShell integration for Visual Studio

(51) Review
Visual Studio
2013, 14
Download (125,668)
11/27/2014
1.0.5
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (51)
Q and A (100)
Sign in to write a review
Sort by:

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.

by Anthony Caragol | June 18 2014

Very nice, love to have this as an option!

by Ryan Mann (TLC) | May 09 2014

This tool works great, but you are running the powershell runspace in the AppDomain.

This causes issues for me because I am developing a powershell module and testing it in the IDE with a script.

So I right click the script and click execute, and it works great. But then I can build my powershell module because Visual Studio has the dll open still because the dll wasn't unloaded at the end of the script.

I suggest that you Create a separate app domain for the script to run in and when it's done (error and all) unload it.

Edit:

Why don't you just have the executor run in a console app and use ProcessStartInfo to run it hidden and get it's output to write to the VS output window? You could compile the console app for x64 and x32 and make the right click execute script have two options "Execute 32" or "Execute 64"

Adam R Driscoll June 03 2014
| Edit |
Delete

This is actually a problem for me as well. :) The problem is with debugging. I need to have access to the variables, breakpoints and debugger state. My hope is to take advantage of the new remote debugging to work around this issue. It's certainly on my radar.

by Matt Wrock | April 21 2014

Awesome extension. Great work here!

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


  • debugging not working properly on my visual studio 2013
    2 Posts | Last post Sun 5:49 PM
    • 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
      
  • Few annoyings things :)
    9 Posts | Last post Wed 10:43 AM
    • I think it's awesome and thank you for making it!
      
      I've tried it for the last couple of days but there are few issues on Visual Studio 2013 Community Edition.
      
      I need to scroll down and up again to get things highlighted again.
      
      I don't get the intellisense immediately.
      
      I feel like ISE is much smarter when it comes to intellisense but maybe it's just because it doesn't work correctly for me.
      
      
      
      
    • I'm experiencing the same symptoms as you. It seemed to work around the .80 versions but not since 1.0
    • Can you guys give some of the latest builds a stab? We have been working a lot with some of issues with editing experience. These are still pre-release but might fix some of the issues you are mentioning. 
      
      https://ci.appveyor.com/project/PoshTools-MSFT/poshtools/branch/dev
    • I've been running the dev branch build for a day now. I am no longer seeing the highlighting problem. Intellisense seems pretty responsive, and Intellisense no longer gets stuck on the screen (and becomes unremovable).
      
      However, the dev build changed the syntax highlighting for me. In the new highlighting all variables are colored Red. The same red that an error is usually colored with. I find this to be disconcerting when working. Is there away to change the syntax highlighting back?
    • I think the highlighting was changed to match the ISE. If it's not, please raise an issue on GitHub. You can always change your font colors in Tools->Options->Fonts and Colors->"PowerShell *"
    • Adam, this dev version resolved most of my issues with highlighting and not stopping at break points so I am very grateful.  Are you looking for other feedback/bugs on this build and if so, where? 
    • Hey Scott, Any feedback you have, please provide on GitHub.
      
      https://github.com/adamdriscoll/poshtools/
      
      Thanks!
    • 1.0.5 has the same behaviour as described Eyal Shilony.
    • Thanks Adam !
      
      This dev version seems also to solve issues I had that are mentioned by steven.
  • Why am I getting errors while writing stuff in comment sections of my script ?
    2 Posts | Last post February 14, 2015
    • I was writing "Fix" in a comment of a ps1 file and got this error when I pressed the "x" key.
      
      I'm using VS12 update 4
      
          <record>334</record>
          <time>2015/02/11 03:17:30.780</time>
          <type>Error</type>
          <source>Editor or Editor Extension</source>
          <description>System.Collections.Generic.KeyNotFoundException: key&#x000D;&#x000A;   &#x00E0; Microsoft.VisualStudio.Utilities.PropertyCollection.GetProperty(Object key)&#x000D;&#x000A;   &#x00E0; PowerShellTools.Classification.PowerShellClassifier.AddTokenClassifications(ITextBuffer buffer, SnapshotSpan span, List`1 classifications, Nullable`1 lastClassificationSpan, IClassificationType gapType)&#x000D;&#x000A;   &#x00E0; PowerShellTools.Classification.PowerShellClassifier.VirtualGetClassificationSpans(SnapshotSpan span)&#x000D;&#x000A;   &#x00E0; PowerShellTools.Classification.Classifier.GetClassificationSpans(SnapshotSpan span)&#x000D;&#x000A;   &#x00E0; Microsoft.VisualStudio.Text.Classification.Implementation.ClassifierTagger.&lt;GetTags&gt;d__0.MoveNext()&#x000D;&#x000A;   &#x00E0; Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.&lt;GetTagsForBuffer&gt;d__5.MoveNext()</description>
        </entry>
    • Interesting. I can't say I've run into this exact issue but I would recommend taking a look at some of the test builds we have been producing to see if it's fixed. 
      
      https://ci.appveyor.com/project/PoshTools-MSFT/poshtools/branch/dev
  • Drop downs do not close
    2 Posts | Last post February 14, 2015
    • Maybe this has already been address but certain drop-downs do not close. For instance, I can do a Get-ChildItem c:\users and I cannot get the drop-down to close. Any ideas? Great extension aside from this issue. Thanks!
    • We have an open item for this. The next version will fix a lot of issues with IntelliSense. 
  • Text Loses Coloring; Autocomplete Quotes
    4 Posts | Last post February 04, 2015
    • Love the plugin!  Recently every project I open will lose the line coloring if I start to type or change anything on that line.  It will only recolor once i scroll away from it, or reload the file essentially forcing visual studio to redraw it.  This does not happen in other languages as i have tried existing and new C# and C++ projects.
      
      Also, is there any plan on implementing autocompletion of parentheses, brackets, and quotes?  Not a huge deal, but nice functionality that other languages have in vs.
      
      Keep up the amazing work!
    • We are working on fixing some of those issues with coloring and the brace\paren\quote matching is in the backlog. Watch the GitHub repo to watch our progress! :D
    • Awesome! Again thank you for the hard work! I may install an old version to get it working again, and I'll watch that repo!
    • @twolfmain - if you're impatient (and brave?) you can grab a build from here: https://ci.appveyor.com/project/PoshTools-MSFT/poshtools/branch/dev/artifacts and send any other feedback you have...
  • intellisense acting funny for me on update 4
    3 Posts | Last post February 03, 2015
    • activitylog.xml
      <entry>
          <record>1142</record>
          <time>2014/12/04 14:35:33.591</time>
          <type>Error</type>
          <source>Editor or Editor Extension</source>
          <description>System.InvalidOperationException: Cannot Filter.  The session is dismissed.&#x000D;&#x000A;   at Microsoft.VisualStudio.Language.Intellisense.Implementation.CompletionSession.Filter()&#x000D;&#x000A;   at PowerShellTools.Intellisense.IntelliSenseManager.Exec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;   at PowerShellTools.Intellisense.IntellisenseController.Exec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;   at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.InnerExec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;   at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.Exec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;   at PowerShellTools.LanguageService.EditFilter.Exec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;   at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.InnerExec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;   at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.Exec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;   at Microsoft.PythonTools.Language.TextViewFilter.Exec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;   at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.InnerExec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;   at Microsoft.VisualStudio.Editor.Implementation.Co
    • OK I managed to fix this.  The issue turned out to be pathing.  Once I had the newer versions of visual studio and SQL Server ahead of the older versions, things started working normally.
    • Can you tell me how you fixed it exactly?
      I'm having the same issue atm.
      Thanks.
  • Console?
    2 Posts | Last post February 03, 2015
    • Where is the console? Where I can just type without having to run the whole code?
    • Found it :/ . "View" -> "Other windows" -> "Powershell debug interactive"
  • VS craches when i right click on folders
    3 Posts | Last post January 29, 2015
    • 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...
  • Pester Tests not showing up in Test Explorer
    2 Posts | Last post January 28, 2015
    • I really like this extension and hope to get the unit testing feature working. I have been trying to use the unit testing feature and have not been able to get the 'Test Explorer' to populate with my pester tests. I have a simple test setup in Script.Tests.ps1  
      
      Describe “Test" {
         It "is a simple test" {
         $false | Should Be $true
        }
      }
      
      When I start the project or save the file it searches for tests in the file and finds the describe block; However, nothing shows up in the 'Test Explorer'. During start-up of my solution Test Explorer appears to be searching for tests, still results in nothing. In order to invoke the test I had to create another script which just has the Invoke-Pester command in it followed by the Visual Studio project directory (Invoke-Pester "C:\Users\Me\Documents\Visual Studio 2013\Projects\testproject\testproject"). This runs and displays the test results in the output window. If I just run Invoke-Pester without specifying the project directory then I get the following output: 
      
      Executing all tests in 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE'
      Tests completed in 0ms
      Passed: 0 Failed: 0 Skipped: 0 Pending: 0
      The program 'Invoke.ps1: PowerShell Script' has exited with code 0 (0x0).
      
      For some reason it tries to execute under the wrong directory. 
      
      Any help you can provide will be greatly appreciated.
      
      My goal is to have 'Test Explorer' invoke my tests and not have to have a separate script to do it.
      
      Thank you!
      
    • I found a temporary solution I thought I would share. Reviewing this blog today and saw a recent post stating there is a location for previous releases. I downloaded Powershell Tools 1.04 and everything is working as expected. I am running Windows 8.1, Powershell Version 4.0 with Visual Studio 2013 Community edition.
  • Breakpoints only work once!
    6 Posts | Last post January 27, 2015
    • This is a great tool set and I would like to get it working again.
      
      I recently installed the VS 2013 Update 4 and updated to the v 1.0.5 of the PowerShell Tools. Now breakpoints only work the the first time a script is run. On subsequent runs they are not hit. To fix this I must restart VS, rather annoying. Any ideas what might be causing this? 
    • I'm looking into this. Microsoft reported this as well. 
    • Any progress on this? Or where can I find the previous version of the PowerShell Tools that has no this problem?
      Thanks,
    • I installed vs2012 with PS tools for vs2012, the same problem re-pro on 2012. I'm new here, the tool looks great otherwise. Is it possible to post a previous version of the tool? Thanks,
    • Previous versions can be found here: https://github.com/adamdriscoll/poshtools/releases
      
      This will be fixed in the next release. 
    • Awesome, 1.0.4 works! Thanks a lot,
1 - 10 of 100 Items