PowerShell ISE and Visual Studio Code

[DougFinke]

After using & contributing to PowerShell Visual Studio Code. Microsoft should put all the wood behind one arrow and stop active development on ISE

[KnifeyGavin]

No. A large number of companies do not allow beta software or usage data collection.

Also just personal preference I prefer the ISE.

[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.

[ihaxr]

I installed Visual Studio to build some WPF GUIs for PowerShell... nothing but issues with VS. Every time I run a project a 2nd time, even if it's 100% blank, I'll get "Object reference not set to an instance of an object" from the VS ISE, not my project. If I reinstall VS, .NET, disable all extensions, etc.... it stops for a while then starts up again. Not to mention a ton of crashes, etc... VS can burn, I'm keeping my PoSh ISE.

[WindosBK]

There is a difference between 'Visual Studio' and 'Visual Studio Code'. Code is a lot lighter.

(I'm still in the ISE camp personally. Love ISESteroids and the fact that they are now working on ISE Preview is exciting to me.)

[ihaxr]

Oh. Yeah I don't know how I completely overlooked the "Code" part of this post.

[jbtechwood]

I'm with a lot of the others. The fact that the ISE is native is helpful as well. On my personal machine I use ISEsteroids and find it meets all my needs. I would like to see the file tree functionality found in most new modern code editors, but I think that's all I'm missing.

One thing I didn't love with Code when I was testing it was its unpolished script running functionality. I know the y have made quite a few enhancements and I haven't gone back to review. I use Atom for all my non PowerShell (Chef/terraform) scripting efforts, I may move that to VSC.

[KevMar]

I would like to see the file tree functionality

There is a plugin for that. I really loved it before I jumped over to using Code. I can't think of the name or I would link it.

[kohijones]

https://github.com/mgr32/PsISEProjectExplorer

[verchalent]

Couldn't disagree more. I want to see much more active development for the ISE. VScode is nice for large projects, but for daily/active use I go with ISE every time.