Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intellisence not working in VSCode PowerShell Extension 21.2.2 on Windows Server 2019 Datacenter Version 1809 #3240

Closed
PaulTheScott opened this issue Mar 12, 2021 · 2 comments
Labels
Resolution-Answered Will close automatically.

Comments

@PaulTheScott
Copy link

I same issue that was identified Issue #179.
(#179) - Or perhaps something is causing the error.

Earlier today, I installed latest versions of VSCode and PowerShell.
OS is Windows Server 2019 Datacenter and all updates are installed current.

Last version of .NET was installed this morning.

All versions of the software are x64.

In the mean time I will also try out the PowerShell Preview plug-in and see if it works there.

I also followed the steps here #179 to get the old PowerShell ISE to work and pick up the intelligence for PowerShell 7.1.3 (64-bit).

Any help on what I might be doing wrong would be greatly appreciated. Thanks!

@ghost ghost added the Needs: Triage Maintainer attention needed! label Mar 12, 2021
@PaulTheScott
Copy link
Author

I have found what was causing my intellisence feature problems in reported in issue #3240.

Issue: Default Intellisence setting are missing from settings.json in VSCode.
Fix: Provided on this webpage: https://code.visualstudio.com/docs/editor/intellisense
Problem Resolved: Yes.

I have followed the instructions here (https://code.visualstudio.com/docs/editor/intellisense) and have added the missing settings to the settings.json file. I then restarted VSCode and found all Intellisence are now working for my PowerShell Extension.

Thank you for providing such a wonderful tool to the world for free. Not everyone can afford to pay extensive license costs involved with proprietary software vendors.

@andyleejordan
Copy link
Member

Thanks @PaulTheScott! Glad you were able to figure this out, and we appreciate the kind words 😊

@andyleejordan andyleejordan added the Resolution-Answered Will close automatically. label Mar 12, 2021
@ghost ghost closed this as completed Mar 13, 2021
@SydneyhSmith SydneyhSmith removed the Needs: Triage Maintainer attention needed! label May 4, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Answered Will close automatically.
Projects
None yet
Development

No branches or pull requests

3 participants