Powershell extension intellisense not came up

[atiedemann]

Hello @ALL,

I'm working with vscode to script my Power Shell scripts but the last days my intellisense of Cmdlets or parameters are not working.

I type import-cs and wait until 30 seconds and nothing comes up.
The same way with parameters....

If I completly remove the extension Powershell 1.4.1 than intellisense are working fine but than not Script Analyser is present and so on. :-(

I check the same issue on a different machine with the same result.
I hope anyone can help me.

Many thanks
Arne

System Details

1498640602-ed165210-2f74-43fb-ae48-5fddad6c84561498640598532.zip

• Operating system name and version: Windows 10 US Enterprise
• VS Code version: 1.13.1
• PowerShell extension version: 1.4.1
• Output from `$PSVersionTable

Name Value

---

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

PS C:> code -v
1.13.1
379d2efb5539b09112c793d3d9a413017d736f89
PS C:> $pseditor.EditorServicesVersion

Major Minor Build Revision

---

1 4 1 0

PS C:> code --list-extensions --show-versions
DavidAnson.vscode-markdownlint@0.9.1
DotJoshJohnson.xml@1.9.2
ms-vscode.PowerShell@1.4.1
ms-vscode.Theme-MarkdownKit@0.1.4

[daviwil]

Strangely I don't see any IntelliSense requests getting sent from the extension. During the session that you sent the logs for, did you try using Ctrl+Space in the file buffer?

[atiedemann]

Hi David, Yes of curse! After I press CTRL+Space I wait several seconds (>=30) and nothin happens. Thanks Arne Gesendet von meinem Windows 10 Phone Von: David Wilson<mailto:notifications@github.com> Gesendet: Mittwoch, 28. Juni 2017 16:22 An: PowerShell/vscode-powershell<mailto:vscode-powershell@noreply.github.com> Cc: Arne Tiedemann<mailto:arne.tiedemann@tiedemanns.info>; Author<mailto:author@noreply.github.com> Betreff: Re: [PowerShell/vscode-powershell] Powershell extension intellisense not came up (#927) Strangely I don't see any IntelliSense requests getting sent from the extension. During the session that you sent the logs for, did you try using Ctrl+Space in the file buffer? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#927 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMIZ6T2pfaY3I2Fs2V_4MYo61S1eN1_Kks5sIl8mgaJpZM4OHsvT>.

[daviwil]

Does this happen in any file you try it in or only in a specific file? What if you create a new .ps1 file and try typing inside of it? Just trying to rule out any issues with the specific file or workspace you're working in.

[atiedemann]

Hi David, yes this is exacly the same way on each machine. But when I create a blank file all is fine until I have code of 50 lines. I think it is depended on ScriptAnalyser because when I resolve any recommandations from Script analyser Intellisense works better but not really fast. If I have from the view of Script analyser a clean Code intellisense need two seconds to display. In an absolutly clean file intellisense works directly on typing – for a parameter. I hope this information helps to troubleshoot. Thanks Arne Von: David Wilson [mailto:notifications@github.com] Gesendet: Mittwoch, 28. Juni 2017 19:07 An: PowerShell/vscode-powershell <vscode-powershell@noreply.github.com> Cc: Arne Tiedemann <arne.tiedemann@tiedemanns.info>; Author <author@noreply.github.com> Betreff: Re: [PowerShell/vscode-powershell] Powershell extension intellisense not came up (#927) Does this happen in any file you try it in or only in a specific file? What if you create a new .ps1 file and try typing inside of it? Just trying to rule out any issues with the specific file or workspace you're working in. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#927 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMIZ6dVks8l-JurP0P3BS40e696IACeXks5sIogngaJpZM4OHsvT>.

[coendewit]

Same here on both of my machines. I tried deinstalling the extension, deinstalling VS Code, deinstalling VS Code and deleting extension folder.

Code analyzer works, but intellisense and go to definition do not.

Logging

vscode-powershell.zip

$psversiontable:

Name	Value
PSVersion	5.0.10586.672
PSCompatibleVersions	{1.0, 2.0, 3.0, 4.0...}
BuildVersion	10.0.10586.672
CLRVersion	4.0.30319.42000
WSManStackVersion	3.0
PSRemotingProtocolVersion	2.3
SerializationVersion	1.1.0.1

code -v

1.13.1
379d2efb5539b09112c793d3d9a413017d736f89

code --list-extensions --show-versions

ms-vscode.PowerShell@1.4.1

[coendewit]

Just confirming that the powershell project causes the failure. Opening just a subfolder of the project solves the problem.

[atiedemann]

Thanks for your reply an this workarround.
I think it will be good when the Script Analyser only work at the editing file not on all open files in VScode.

Have a nice day
Arne