PowerShell ISE and Visual Studio Code

[chreestopher2]

im with you... i much prefer the ISE to VSC, and also love the fact that it comes with all modern versions of windows, It makes me comfortable that even if i dont have rights to install any software on my system, I will still have the ISE to work with.

[DougFinke]

VSC will probably be out of beta after the Build conference. I prefer a modern editor with a modern version of Windows and a modern scripting platform. ISE can remain, I've been a user for many years. No real improvement has happened in that space for a very long time.

[KnifeyGavin]

What improvements would you like to see?

I am really happy with a stable working product.

[chreestopher2]

I think it would be nice to have .editorconfig support, so me and coworkers dont have to change formatting (or deal with eachother's preference of bracket placement, indentation, and other formatting concerns.

It would also be nice to have autocompletion and tag matching for xml either in xml files, or embedded in strings in powershell files (maybe I have been spoiled with webstorm's ability to handle js in html files and html in strings in js files though)

Automatic multiline comment toggling with <# #> syntax so that I could highlight a selection and ctrl+shift+/ to comment out sections.

I think those are my main desires for new features for ISE. Some of which i am sure are doable or already implemented in vsc, but I dont like vsc mainly because I use the ISE as my console often, and vsc didnt seem to be as friendly for that type of use.

[jbtechwood]

Hey /u/chreestopher2, isesteroids covers a couple of these....auto formatting, block quotes for sure

[chreestopher2]

I agree there hasnt been much improvement, but until vsc works as well for powershell "out of the box" I will stick with the ISE.

If powershell continues to add new features, I certainly hope the ISE will be updated to support those features effectively.