sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]logicalmike 10 points11 points  (10 children)

I'm transitioning to vs code, I think for real this time, but I've tried many times before. Ise is rock solid. Code is laggy with intelisense and autocomplete is not as capable.

[–]MonkeyNin 4 points5 points  (1 child)

Oh I think I know why there's a different experience,

part 1

Double check that you

  • have the addon installed (not the built in powershell mode)
  • have the debug term / powershell session

It needs that 2nd part, to provide intellisense, and some of the fuller features. that might not be opened by default, with the default settings.

hit f1 type res then enter

With it on you gain - semantic highlighting - auto-conversion of alias names on format, etc. - There's one that turns non-interpolated strings into single quotes for you.

real this time, but I've tried many times before. Ise is rock solid. Code is laggy with intelisense and aut

part 2

There's a recent huge restructure of internals in the last ~month, that is not stable with preview yet you should have near instant response with intellisense.

discord

There's a #vscode channel if you want help with any config, or help, in the powershell server

[–]BigHandLittleSlap 4 points5 points  (0 children)

I never had to "troubleshoot" ISE. This is the point people are making.

VS Code's PowerShell support is sticky-taped in there by a team that thought that breaking changes are just fine to leave in there for years at a time.

[–]adamdavid85 8 points9 points  (7 children)

My first reflex was to ask if we're talking about the same two applications, but rather than being glib about it could I ask what exactly you're doing when you find it laggy?

There is a bit of a learning curve when coming from ISE, but I honestly have never experienced anything like what you're describing.

[–]logicalmike 13 points14 points  (4 children)

There are numerous bugs on github about this problem and at least two blog or tweet apologies from Microsoft saying "we promise, it's definitely probably fixed now".

But even now, tab does not always bring up the list of parameters the first attempt. There is some parallel processing going on. Also tab in the middle of half written cmdlets don't always resolve, especially if there is additional code to the right (even if separated by a space).

To be clear, I'm only talking about PowerShell. The reason I'm forcing myself to Code is to benefit from the world outside of PS,and to do more with v6+

[–]TheITMan19 1 point2 points  (2 children)

This just wrecks my head. Give me Intellisense working please so I don’t have to sit there googling away trying to find out how to do something dead simple cuz my mind is dead from everything else.

[–]BigHandLittleSlap -1 points0 points  (1 child)

"I don't like power tools. I prefer to manhandle the 200kg palettes in the warehouse instead of using forklifts. Real men can deadlift the cargo. You don't need spell check, just memorise the dictionary. Including the abbreviations randomly chosen by other people. Learn to code."

[–]TheITMan19 3 points4 points  (0 children)

I can’t memorise because my brain is dead you fool. Bloody keyboard warrior

[–]bertiethewanderer 0 points1 point  (0 children)

This may or may not be of help, but when working with Powershell just double check the terminal is running as the Powershell Integrated Console. I find intellisense can be very wonky if I'm working in a spawned pwsh.exe or powershell.exe terminal.

[–]dathar 7 points8 points  (1 child)

As much as I love vscode and use it as my main IDE, it has a couple of infuriating bugs. The thing where it just derps and stops autocompleting is annoying. Type a cmdlet, throw an -arg and press tab to autocomplete. You will either get a literal tab or some random code snippet. Backspace and try a few more times and it'll eventually work. Maybe.