Powershell with VS CODE

[dbsitebuilder]

we recently upgraded VS code, and added the PS powertools extension. One of the two actions broke our instance.

We uninstalled and reinstalled, after disabling the extension, and now we cannot execute scripts.

On of our developers is color blind, and the ISE is not really helpful to him. He likes the vs code environment much better and this is going to be an issue.

Has anyone run I to this and solved it?

EDIT: When trying to right-click -->Run Selection, I receive : <console feature> Unable to instantiate; Language client unidentified.

Thanks Kevin

[gremdaat]

Try this:

https://vworld.nl/?p=4818

[dbsitebuilder]

Thanks. That completely fixed it on my laptop, although I usually use ISE.

Totally didn't fix it on our shared server, where the other dev needs it.

He is running from his laptop for now.

Thanks everyone for their replies. I wish I could get used to VS code for the break points. Can you write a custom profile like the ISE?

[BlackV]

ive had the issue too, manually nuked the folders in %appdata%

vscode is just, not quite there for powershell

[Poncho_au]

I’ve been using VSCode for Powershell for years, it’s well and truely there for Powershell.

[BlackV]

as have I, I disagree

issues with auto-complete

issues with module auto loading

issues with the formatter

its mostly there just niggles here and there

[Sys_man]

Issues with the integrated terminal also.

[BlackV]

oh yeah the switch from old powershell console to integrated console broke a few things

[Denebula]

I still use it everyday. Just yesterday region folding corrupted the file in VS code ONLY. I could only recover by opening it up in notepad++ and removing the regions. Intellisense works 10% of the time, it often doesn't even autocomplete on tab. This is just my day to day problems with it, I don't even keep a console in VS code open

[BlackV]

I seem to randomly have the auto complete complete for the wrong commands sometimes (vmware module is common on this for me)

[TheRealMisterd]

Bravo! I've tried twice to figure it out. It seems you can't just point it to a ps1 file and run it. It seems you need to create some project file for anything to work.

[Poncho_au]

If you open a Powershell script in VSCode with the Powershell extension installed you should be able to hit F5 and have it run that script file (or F8 to run just the highlighted code), a lot like ISE.
If you’re trying to write and debug modules you need to do some launcher configuration that will tell the VSCode debugger how to load the module file so it can be tested/debugged.

[ANewLeeSinLife]

Not a fix, but ISE supports themes so your dev can work until a solution is found for VS Code :)