PowerShell extension uses PSScriptAnalyzer settings file - Cannot update rules

[PowerDBAKlaas]

I had this error when doing: <ctrl>+<shift>+P, PSScript...

After Uninstall and reinstall the Powershell extension ( version 1.3.2, the same as it was before), there's another issue:

System Details

• Operating system name and version: Windows 10.0.14393
• VS Code version: 1.13.1
• PowerShell extension version: 1.3.2
• Output from $PSVersionTable:
  Name Value

---

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

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

Major  Minor  Build  Revision
-----  -----  -----  --------
1      3      2      0


PS C:\scripts> code --list-extensions --show-versions
ms-mssql.mssql@1.0.0
ms-vscode.PowerShell@1.3.2

Issue Description

I am experiencing a problem with PSScriptAnalyzer: cannot update the rules

Attached Logs

1497967294-c7966750-26b9-4c1a-88bf-382515625aa61497967292400.zip

[PowerDBAKlaas]

Actually, the thought that something is wrong, started with noticing that the warning and error count ( in the left lower corner) were and are always 0.

[PowerDBAKlaas]

OK
"powershell.scriptAnalysis.settingsPath": "bin//PSScriptAnalyzerRules.psd1",
was set to a non-existing file, so this was my own fault.
Maybe if the error message could say "file not found" I would realize that sooner than with "cannot update the rules"

[daviwil]

Hey Klass, sorry for the delay in response. I'm glad you figured out the issue! You're right, we should indicate that the settings file is missing, I'll reopen this issue so we can track a fix for that.