PSScriptAnalyzer

We have made a lot of changes since our first release of the tool in WMF5. In the next page "Fixes, Features and New Rules since Feb WMF 5.0", you can see a list of changes that we've already made into our engine.

On this page you will find a list of items that are in our current development plan. We welcome contributions on engine improvements and additional community rules.

PSScriptAnalyzer is an evolving product and we hope that this tool will help PowerShell script developers to build better scripts.

##Planned changes:

Add RuleSet functionality

• Do not have to type full names when include/exclude rules

• Group rules together to apply Invoke-ScriptAnalyzer

Change format of Get-ScriptAnalyzer (Completed)

• Add rule severity in each rule

Suppression

• Allow user to suppress rule(s) on specified parts of the script (eg. Functions, classes or the entire script)

• Output suppressed warnings

Retrieve Customized Rules Recursively

• Retrieve customized rules recursively under given directory when -Recurse is used.

##New Features Added to PSScriptAnalyzer

Changes to the Engine

• Engine will continue to run rules against scripts/modules and report any rule exceptions as as non-terminating errors (such as parser errors)

• If -Recurse is supplied, PSScriptAnalyzer will do a recursive checking on files within any sub-folder of the specified directory.

• Suppression functionality Have similar functionality support as FxCop that allows the user to suppress certain rules on certain functions/modules/files within scripts.

• Wildcard support for both Invoke-ScriptAnalyzer and Get-ScriptAnalyzerRule eg. Invoke-ScriptAnalyzer -IncludeRule PSAvoid*

• Added filter to get rules by severity

###For more feature requests and bug reports, please go to Issues