search

PowerShell / vscode-powershell

Provides PowerShell language and debugging support for Visual Studio Code
https://marketplace.visualstudio.com/items/ms-vscode.PowerShell
MIT License
1.71k stars 488 forks source link

PowerShell Intellisense does not work #1575

Closed elliottgaryusa closed 6 years ago

elliottgaryusa commented 6 years ago

System Details

VSCode Version: 1.28.0 (user setup) Commit: 431ef9da3cf88a7e164f9d33bf62695e07c6c2a9 Date: 2018-10-05T14:58:53.203Z Electron: 2.0.9 Chrome: 61.0.3163.100 Node.js: 8.9.3 V8: 6.1.534.41 Architecture: x64

VSCode extensions:

Darfka.vbscript@1.0.4 formulahendry.code-runner@0.9.4 GrapeCity.gc-excelviewer@2.1.26 KnisterPeter.vscode-github@0.30.0 luggage66.VBScript@0.0.2 ms-vscode.csharp@1.16.2 ms-vscode.powershell@1.9.0

PSES version:

PowerShell version:

Name Value

PSVersion 5.1.14409.1012 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.14409.1012 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1

System Details Output

Issue Description

I am experiencing a problem with... Microsoft PowerShell extension 1.9.0

How to reproduce:

  1. Open new file with .ps1 extension
  2. Enter Get-Child (or any partial PowerShell command)
  3. Result, no suggestions and no code complete
  4. Enter a complete PS command like Get-ChildItem -
  5. Result, no parameter suggestions

Background: This seems to have started since the latest VSCode update 1.28.0 (user setup). The code snippets seem to work OK but not the commands themselves. I tried re-installing the extension but it did not help.

Expected Behaviour

I would expect normal intellisense behavior as before, which worked great before VSCode 1.28.0

Actual Behaviour

Intellisense does not work at all. Snippets seem to work OK.

Attached Logs

rjmholt commented 6 years ago

Hi @elliottgaryusa, thanks for opening an issue.

Can you please attach your logs, as described in the troubleshooting docs? Without them, reproducing the issue (and fixing it) is much harder.

We ship independently of the VSCode version, so unless a breaking change has occurred in VSCode, that shouldn't affect the extension's functionality. (We develop against the insiders version so that we are aware of those). So maybe worth trying with the extension installed in VSCode Insiders as well?

elliottgaryusa commented 6 years ago

I tried both Verbose and Diagnostic logs but it didn’t generate any entries.

Gary Elliott

On Oct 11, 2018, at 3:55 PM, Robert Holt notifications@github.com wrote:

Hi @elliottgaryusa, thanks for opening an issue.

Can you please attach your logs, as described in the troubleshooting docs? Without them, reproducing the issue (and fixing it) is much harder.

We ship independently of the VSCode version, so unless a breaking change has occurred in VSCode, that shouldn't affect the extension's functionality. (We develop against the insiders version so that we are aware of those). So maybe worth trying with the extension installed in VSCode Insiders as well?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

elliottgaryusa commented 6 years ago

Here's the logs but, for some reason, they are out of date (10/3) and do not show any current activity. I changed the logging to both Verbose and Diagnostic with no change.

EditorServices.log vscode-powershell.log

elliottgaryusa commented 6 years ago

I noticed that intellisense seems to work as expected on another pc that I upgraded from VSCode 1.27.1 to 1.28.0. So it appears that my install is goofed up somehow.

elliottgaryusa commented 6 years ago

A complete uninstall then new install of all extensions and VSCode seems to have fixed the problem. So now I'm not sure if the root of the issue is with the extension or VSCode. The issue is resolved for now.