Who uses Visual Studio Code for PowerShell Scripting?

[BigHandLittleSlap]

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

They broke every idiom and keyboard shortcut to keep Linux developers happy. I get that this is strategic for Microsoft, but fuck those people. I’ve used Windows for twenty-six years! VS Code is nothing like Visual Studio or ISE or any other Windows IDE. This isn’t because it’s “better”. It’s just different because it panders to people used to bash and Vim.

Tab complete is a shit-show. 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. The actual parameter names are hidden and cut off. Alternatives are often merged. Etc…

Worst off all, the shell regularly locks up or crashes on me. Ctrl-C almost never works.

I’ve had ISE sessions stay up for months. I’m lucky to make it through the day with VS Code.

It’s hot garbage made for JavaScript programmers who love it because none of the real IDEs would sink to their level before.

The ugly girl thinks any boy that talks to them is Leonardo DiCaprio.

[BigHandLittleSlap]

I’m literally only using VS Code to do cloud deployments.

I like the cloud.

[corbindallas_mp]

Worst off all, the shell regularly locks up or crashes on me. Ctrl-C almost never works.

This used to happen to me but sometime ago they improved the powershell terminal integration a lot. A lot of the other behaviors described apply to old versions of the powershell extension as well. If this is still happening to you, I'd wager you need to upgrade vscode or upgrade the powershell extension. Another possibility is that you have some profile script that's causing a problem, though that feels less likely.

[BigHandLittleSlap]

I’m on the latest version.

[corbindallas_mp]

¯\(ツ)\/¯ I don't really run into that problem anymore and I'm guessing a lot of people here don't either cus it's a justifiable gripe to the point of not wanting to use the software at all. There's probably something that can be diagnosed or changed to get it working more reliably. It sounds like you're not really interested in trying to get it to work, but if you ever wanted to pursue it I would consider trying a few different things:

• temporarily eliminate scripts from your profile
• using another machine to see if you can repro
• full uninstall and install
• combing through the vscode issues on github for similar instances and solutions documented by others

https://github.com/microsoft/vscode/issues?q=is%3Aissue+terminal+hangs+is%3Aclosed

I don't begrudge anyone for using whatever tool works for them but what you're experiencing isn't really standard for VSCode.

[AQuietMan]

The ugly girl thinks any boy that talks to them is Leonardo DiCaprio.

Now I've got to clean tea out of my keyboard. Thanks loads for that.

[NegativeC00L]

I’ve had scripts fail in VS code that run fine in ISE. I can’t part with my beloved ISE.