PowerShell integration for Visual Studio

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

by CCFR2 | April 03 2014

by Greg Prosch | September 12 2012

This *could* be a nice tool but like others have noted it is still crashing and the intellisense implementation is more hindrance than help. It frequently auto-completes stuff whether you want it to or not. Going to have to uninstall until there is a new version to try.

by Chris Shouts - Centare Group Ltd | August 01 2012

Excellent idea, but frequent crashes make it more trouble than it is worth. Additionally, the IntelliSense does not understand comments and keeps getting in the way when writing English. Needs some more polish to be truly useful.

by Russ Shearer | January 08 2012

Excellent. Exactly what I was looking for.

Is there anything the community can help with?

by Mark Michaelis - IntelliTect | October 30 2011

Ian - you have hit another one out of the park. Great Job!!

by Silicon Dragon | October 27 2011

This extension crashes frequently on my dev box (VS 2010, no other extensions installed) and the intellisense is pure crap, injecting the wrong text over 90 percent of the time. I got so tired of fixing its mistakes that I uninstalled the extension after only 5 minutes of usage.

It shows great promise, however, hope the developer fixes the bugs and--most especially--changes the intellisense auto-completion to stop injecting text every time I hit the space bar. (Auto-completion should fire on TAB and arrow-key events, not SPACE events, grrr.)

The only thing that works relibably is color-syntaxing. /yawn

by Rich Prescott | September 01 2011

by YannDuran | August 24 2011

What an AMAZING tool! I can't wait to get the opportunity to get to try it out, from what I saw on your demo video.

Every single user of VS who does *anything* with PowerShell should have this.

Well done!!! An absolute 5+ for me.

by A Sherwood | August 20 2011

Goodbye PowerShell ISE!

by fschwiet | August 17 2011

Thanks Ian!

by Bart Barcus | August 17 2011

by Aaron Weiker | August 15 2011

I love having syntax highlighting and code folding in visual studio. This extension makes me happy as a developer that maintains powershell scripts on a regular basis.

by Gordon Beeming | August 14 2011

When I click on properties of a ps project in the solution I get the error

Microsoft Visual Studio
Could not load type 'PowerStudio.LanguageService.Project.GeneralPropertyPage' from assembly 'PowerStudio.VsExtension, Version=, Culture=neutral, PublicKeyToken=9fb17f1436bedd1a'.

Still pretty cool idea, but doesn't run for me. not sure if the error above is linked to the problem

Ian Davis August 15 2011
| Edit |

This issue has been fixed in 1.0.2:


Please update via the Extension Manager.


Sign in to start a discussion

  • VS2012 and VS2013
    1 Posts | Last post August 31, 2013
    • Will this work with VS2012 and VS2013?
  • works is I use VS shell only?
    4 Posts | Last post September 29, 2011
    • will it work if I only have the VS shell only? I downloaded and I'm not sure it was correctly installed... any ideas? thanks
    • The next version will work in the Visual Studio 2010 Integrated Shell. It will not currently install into the shell as that platform was not set up. Thank you for bringing this up. I will try to get an update out shortly. Here is the link for tracking this issue: https://github.com/IntelliTect/PowerStudio/issues/11
      Ian Davis
    • This has been implemented in 1.0.8. Let me know if how it works for you. - Ian
    • it works well; thanks for the effort ;-)
  • Performance Issues
    2 Posts | Last post August 15, 2011
    • There are a couple of known performance issues when typing and scrolling in large files. This will be addressed shortly.
    • This has been fixed in 1.0.6
  • Command Completion
    2 Posts | Last post August 15, 2011
    • Command completion is currently disabled until the performance issues are resolved.
    • This has been fixed in 1.0.6