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

Intellisense not working #179

Closed
jahshuah opened this issue May 14, 2016 · 6 comments
Closed

Intellisense not working #179

jahshuah opened this issue May 14, 2016 · 6 comments

Comments

@jahshuah
Copy link

Maybe I'm new, maybe I missed something, but I cannot for the life of me figure out how to get Intellisense working with this extension. I'm running VSCode on a new Win 10 build (installed yesterday) and the latest version of both VSCode and the PowerShell extension.

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

@daviwil
Copy link
Contributor

daviwil commented May 14, 2016

Hey @jahshuah, no problem. The first thing we should do is check the logs. Open up your VS Code User Settings (File -> Preferences -> User Settings) and insert this line into the file that appears in the pane on the right side:

"powershell.developer.editorServicesLogLevel": "Verbose"

Now restart VS Code and open a PowerShell file and try getting IntelliSense a few times. Now you should be able to navigate to this path on your hard drive:

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

There should be a file there called EditorServices.log. Could you drag and drop it into your reply to this issue?

@jahshuah
Copy link
Author

jahshuah commented May 14, 2016

So, it took restarting VSCode twice to get IntellSense working, but it works now. You'll find the EditorServices.log file attached. Not sure what changed after the second restart of VSCode, but as I said, it's working now. Thanks for the assist.

EditorServices.txt

@daviwil
Copy link
Contributor

daviwil commented May 14, 2016

Yep the logs look good to me now. Not sure why you needed to restart VS Code a couple of times, but I've seen instances where a fresh install of the extension doesn't get activated correctly the first time. Not sure if it's a VS Code bug or something else.

I'll close this issue for now since it seems to be working for you. Let me know if you run into it again and we'll debug it further!

@daviwil
Copy link
Contributor

daviwil commented May 15, 2016

Hey @jahshuah, turns out that there's actually a bug here due to a timing issue in initialization. Since it's likely that you'll see this happen again I just wanted to let you know that I'm looking into it. Tracking the fix using bug #183.

@jahshuah
Copy link
Author

@daviwil You're so right. I just opened VS Code and sure enough, no IntelliSense. I'll follow #183 going forward. Thanks again for your help.

@daviwil
Copy link
Contributor

daviwil commented May 16, 2016

Just fixed it! Will be shipping an update in an hour or two.

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