Bring PowerShell support to the editor
In 2005 there was VBScript support, and the general consensus is that PowerShell is the wave of the future for scripting. Why can't it be brought into VS as a supported language with IntelliSense? It seems like the wheel was reinvented when the PowerShell ISE was developed when it can also be done in VS.
Visual Studio 2015 comes with the option of installing PowerShell Tools for Visual Studio during setup. This provides editing and debugging support for PowerShell.
Bertrand Le Roy – Program Manager
I stopped by to say Thank You!
Victor Vogelpoel commented
My vote! I'd love to find native editing and debugging support for PowerShell in Visual Studio!
However, the ISE editor has its place on each computer where PowerShell is installed.
Powershell-suppert in Visual Studion would be GREAT, but it has to support 64-bit powershell....
Microsft is that not native support for PowerShell in VisualStudio, I want to think a joke of something.
It is a Windows shell script, even though it has already used to Microsoft's own various products of functions.
All you need's native support rather than expansion.
Mark Wilson-Thomas commented
Hi contributors. At this point we don't have any plans to add in-box PowerShell Language support to Visual Studio, since Adam Driscoll's extension covers this requirement well.
Mark (Visual Studio Editor Team)
Keith Hill commented
Adam Driscoll has done this. Look for "PowerShell Tools for Visual Studio" in the extension manager. It's quite nice!
Nicolas Uthurriague commented
100% Agree. We're developing a complete PowerShell-based solution with scripts, modules and Dlls but we need to rely on an external tool for debugging or editing PowerShell components (PowerGUI). This is far from ideal.
Got my vote.
In addition to "ps1" intellisense and syntax highlighting support, please add support for "cmd" and "bat" files too.
I agree with guys. Please dump ISE and pack a light-weight (express) VS version in WindOS (with support for JS, HTML, Text, PS1, CMD, BAT, CSS etc.)!
I totally agree with Kent. Debugging and handling module with VS is currently quite hard with current VS extension style. Full intellisense support for .NET Class is what PowerShell developer really wants.
I agree with Kent. Dump the Powershell ISE and let us use Visual Studio.
Kent Boogaart commented
Think some peeps are misunderstanding, or perhaps I am. The point is not to allow the execution of a PS script as part of a build event, but to enable editing of PS scripts with full syntax highlighting/Intellisense/debugging et cetera. Currently one must download a separate tool to do this, and I completely agree that this should all be in VS. At worst, a separate flavor of VS.
Yes, it needs to be fully supported in VS Studio like C#.
Consider: Your current object browser view, or your current project bindings class view, interactive and scriptable...
Visual Studio: Interactive PowerShell'ing IDE !
please bring back dimgray borders and white background !!!
You can still run powershell commands on Project Build Events. Here is how I do that:
powershell -file "$(SolutionDir)tools\pack.ps1" $(SolutionDir) $(ProjectPath)
But I agree that it would be great to have OOB support for this.
I don't even use this feature and still voted for it. Powershell should be everywhere. However, you could just put your powershell build script in your project (for quick editing), and set the pre/post build event to call that script (i.e. powershell.exe $(ProjectDir)\postbuild.ps1) right?
Jeremie Chassaing commented
Sorry, my phone sent this one without my consent...
The point is to better integrate powershell as an automation mean in VS, to go further that what is possible today with the package manager console of NuGet.
Provide better console,
Add better automation than raw DTE com interface.
Use it more widely in the whole ide.
Michael Paterson commented
I would totally vote for this too if I hadn't already used them all. Great idea.
@jeffpierson - I added a vote for you, just don't tell anyone ;-)
Visual Studio PM
I would vote on this but all my votes are used up.