Invoke-ScriptAnalyzer throws error

[chriskuech]

PSScriptAnalyzer throws an error "Object reference not set to an instance of an object" when analyzing the hash literal in the following line.

$MyObj | % { @{$_.Name = $_.Value} }

[bergmeister]

Does not repro for me using the latest version 1.16.1 on PowerShell 5.1 for Invoke-ScriptAnalyzer -ScriptDefinition '$MyObj | % { @{$_.Name = $_.Value} }' and the same if I put your line into a ps1 file.
Please provide more details.

[chriskuech]

No longer repros for me either

[bergmeister]

Ok. Thanks. Could you otherwise try it on the file in which it was originally? I would be happy to look into it even if it's quite a long script since I recently opened a new PR that allows me to attach the Debugger in VS to it very easily.

[chriskuech]

I just tried to repro this issue more intensively.

I ran combinations of

• Invoke-ScriptAnalyzer . -Recurse vs Invoke-ScriptAnalyzer -ScriptDefinition $snippet
• Absense vs present of $snippet in a file
• Absence vs presence of .\PSScriptAnalyzerSettings.psd1

The error case is only when PSScriptAnalyzerSettings.psd1 is defined and the snippet is in a file. The associated PSScriptAnalyzerSettings.psd1 is here

[bergmeister]

Sorry, it still does not repro for me using your settings file
with script.ps1 having the content $MyObj | % { @{$_.Name = $_.Value} }

Invoke-ScriptAnalyzer -Path .\script.ps1 -Settings (get-content .\PSScriptAnalyzerSettings.psd1)

I have tried with and without -Recurse

[chriskuech]

Can you try explicitly testing Invoke-ScriptAnalyzer . -Recurse with the correct file system setup?

[bergmeister]

Aha. I found that I can reproduce now with Invoke-ScriptAnalyzer . but only if the PSScriptAnalyzerSettings.psd1 is in the current directory. So my guess is that this is where it comes from (PSScriptAnalyzer also analyses manifest files by default). Thanks for your persistence. I can now finally look into it.