PSScriptAnalyzer not working correctly on Visual Studio Code

[vandreytrindade]

System Details

• Operating system name and version: Windows 10 1803 build 17134.191
• VS Code version: 1.25.1
• PowerShell extension version: 1.17.1
• Output from $PSVersionTable:

Name                           Value
----                           -----
PSVersion                      5.1.17134.165
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.165
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

More information:

code -v
1.25.1
1dfc5e557209371715f655691b1235b6b26a06be
x64

$pseditor.EditorServicesVersion
code --list-extensions --show-versions

$PSVersionTable
1.25.1
1dfc5e557209371715f655691b1235b6b26a06be
x64

Major  Minor  Build  Revision
-----  -----  -----  --------
1      8      2      0
emmanuelbeziat.vscode-great-icons@2.1.39
ms-vscode.PowerShell@1.8.2

Key   : PSVersion
Value : 5.1.17134.165
Name  : PSVersion

Key   : PSEdition
Value : Desktop
Name  : PSEdition

Key   : PSCompatibleVersions
Value : {1.0, 2.0, 3.0, 4.0...}
Name  : PSCompatibleVersions

Key   : BuildVersion
Value : 10.0.17134.165
Name  : BuildVersion

Key   : CLRVersion
Value : 4.0.30319.42000
Name  : CLRVersion

Key   : WSManStackVersion
Value : 3.0
Name  : WSManStackVersion

Key   : PSRemotingProtocolVersion
Value : 2.3
Name  : PSRemotingProtocolVersion

Key   : SerializationVersion
Value : 1.1.0.1
Name  : SerializationVersion

Issue Description

I have opened an issue on the PSScriptAnalyzer github page, and they told me to post it here:
Link to the Issue

Steps to reproduce

• Open Visual Studio Code
• Create a new PowerShell file
• Press CTRL+SHIFT+P and select PowerShell: Select PSScriptAnalyzer rules
• The list is shown... If you type in the new file: "gc C:\Dell", it highlightes the "gc" command correctly.
• Then open an existent file on Visual Studio Code
• Press CTRL+SHIFT+P and select PowerShell: Select PSScriptAnalyzer rules
• Nothing happens and typing "gc" or any other command that triggers PSScriptAnalyzer, is not working anymore... I have to close Visual Studio Code.
• Trying to configure settings.json using this:
  "powershell.scriptAnalysis.settingsPath": "c:\users\lee\PSScriptAnalyzerSettings.psd1"
  the first part doesn't turn blue (accepeted command) and it returns something like path not found.

Expected behavior

• Automatically start analyzing the code on any file new or opened.
• Being able to configure settings.json

Actual behavior

• Not being able to use PSScriptAnalyzer
• Not being able to configure it using settings.json

• Environment data:

Diretório: C:\Program Files\WindowsPowerShell\Modules

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     1.17.1     PSScriptAnalyzer                    {Get-ScriptAnalyzerRule, Invoke-ScriptAnalyzer, Invoke-Formatter}

    Diretório: C:\Users\vpereira\.vscode\extensions\ms-vscode.powershell-1.8.2\modules

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     1.17.1     PSScriptAnalyzer                    {Get-ScriptAnalyzerRule, Invoke-ScriptAnalyzer, Invoke-Formatter}

Attached Logs

Follow the instructions in the README
about capturing and sending logs.

[vandreytrindade]

In the PSScriptAnalyzer github page, @kilasuit noticed that it has a delay to load the extension. In my environment it took more than 20 seconds to start. Even though the settings.json continues to not recognizing that parameter.

[rjmholt]

This looks like a performance issue with PSScriptAnalyzer. Ideally we can solve it with some of the ongoing work we're doing at the moment.

[rjmholt]

#1569 might also be relevant here