how to use visual studio code for powershell

I prefer the way VSC has all the variables down the side during a debug session so you can expand them yourselves.

Sometimes it might quickly flash and other times not appear at all. I think ISE is one of those programs that if you grew up with you're fine with but as I started straight with VSC I struggle with ISE when I have to troubleshoot something server-side.įor example, the other day I had to debug something in ISE and the step in/over options are hidden in a sub menu, I also found hovering over a variable to get the value was intermittent. I use VSC - There was a while where I had an issue with Powershell refusing to load in VSC but that seems to be a lot more stable now. The ugly girl thinks any boy that talks to them is Leonardo DiCaprio. It’s hot garbage made for JavaScript programmers who love it because none of the real IDEs would sink to their level before. I’m lucky to make it through the day with VS Code. I’ve had ISE sessions stay up for months. Worst off all, the shell regularly locks up or crashes on me. The actual parameter names are hidden and cut off. Sometimes it just barfs up a page of random garbage that’s utterly irrelevant in 99.99% of the contexts in which tab complete would be used. It’s just different because it panders to people used to bash and Vim. I’ve used Windows for twenty-six years! VS Code is nothing like Visual Studio or ISE or any other Windows IDE.

I get that this is strategic for Microsoft, but fuck those people. They broke every idiom and keyboard shortcut to keep Linux developers happy.

I’m forced to use VS Code for PS Core support and I hate it.

How to use visual studio code for powershell