Skip to content

Intellisense Broken #50

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

Closed
0x4c6565 opened this issue Dec 18, 2015 · 3 comments
Closed

Intellisense Broken #50

0x4c6565 opened this issue Dec 18, 2015 · 3 comments

Comments

@0x4c6565
Copy link

With 2 fresh installations on 2 seperate Windows 7 installations, Intellisense appears to be broken, with no suggestions offered for Cmdlets or variable names.

Both were installed via the built in extension installer

@daviwil
Copy link
Contributor

daviwil commented Dec 18, 2015

Hi Lee, currently this extension is supported only on machines that have Windows Management Framework 5.0 installed (which contains PowerShell v5). Since this is a Windows 7 machine, can you confirm what version of PowerShell you're running by grabbing the results of the $PSVersionTable variable? We intend to support both PowerShell v3 and v4 in the future.

Also it might be helpful if you send the log file from the language service, you can find that here:

c:\Users\<yourusername>\.vscode\extensions\ms-vscode.PowerShell\bin\EditorServices.log

E-mail that to my GitHub username @microsoft.com and I'll take a look.

@0x4c6565
Copy link
Author

Hi,

Apologies, I must have missed the PS 5 requirement! I'll close this now.

Thank you for your response :)

@daviwil
Copy link
Contributor

daviwil commented Dec 18, 2015

Give PS5 a try and if it doesn't work, feel free to reopen the bug!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants