Question 1

How to disable a specific rule in PSScriptAnalyzer?

Accepted Answer

Use the -ExcludeRule parameter with Invoke-ScriptAnalyzer, e.g., Invoke-ScriptAnalyzer -Path script.ps1 -ExcludeRule PSAvoidUsingInvokeExpression. You can also suppress rules inline with comment-based suppressions for finer control.

Question 2

Can PSScriptAnalyzer analyze PowerShell 7 scripts?

Accepted Answer

Yes, it fully supports PowerShell 7. The build script allows targeting PowerShell 7 with the -PSVersion 7 parameter, and rules are updated to cover newer PowerShell features and best practices.

Question 3

What's the difference between PSScriptAnalyzer and PowerShell ISE's analyzer?

Accepted Answer

PowerShell ISE had a basic, built-in analyzer that's now deprecated. PSScriptAnalyzer is a standalone, more comprehensive tool with a larger rule set, active development, and better integration for modern editors and CI/CD pipelines.

Question 4

How to integrate PSScriptAnalyzer with Visual Studio Code?

Accepted Answer

Install the PowerShell extension for VS Code, which includes PSScriptAnalyzer support. After installing the module, configure the extension settings to enable script analysis on save or as you type for real-time feedback.

Question 5

Are there common false positives with PSScriptAnalyzer?

Accepted Answer

Yes, rules like PSAvoidUsingPositionalParameters can flag legitimate code. To manage this, you can customize rule severity, use exclusions, or implement comment-based suppressions to reduce noise in your analysis.

Question 6

How to create a custom rule for PSScriptAnalyzer?

Accepted Answer

Custom rules can be written in PowerShell or C# by implementing the IScriptRule interface. The documentation on learn.microsoft.com provides guides and examples, though the fragmented docs might require extra effort to navigate.

PSScriptAnalyzer

What is PSScriptAnalyzer?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions