Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Get-ScriptAnalyzerRule throws exception despite common parameter '-ErrorAction SilentlyContinue' is defined

Open
#1,876 0 comments 0 reactions 1 assignee View on GitHub

@bergmeister is already working on this.

Since Dec 21, 2022.

Assessment

This issue has not been assessed yet.

Description

Issue-Bug

When running the command provided in the reproduce an exception is thrown. This is unexpected and undesirable.

It would be great when exceptions could be silenced by specifying common parameter -ErrorAction SilentlyContinue.
The documentation of this cmdlet describes <CommonParameters> can be used.

Steps to reproduce

Get-ScriptAnalyzerRule -CustomRulePath C:\someExistingPathWithoutPSSARules\ -RecurseCustomRulePath -ErrorAction SilentlyContinue

Expected behavior

#no output

Actual behavior

Get-ScriptAnalyzerRule: Exception of type 'System.Exception' was thrown.

If an unexpected error was thrown then please report the full error details using e.g. $error[0] | Select-Object *

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      7.3.1
PSEdition                      Core
GitCommitId                    7.3.1
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

> (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() }
1.21.0
Dominant language
C#
Stars
2.2k
Forks
415
Avg merge
13h 1m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PSScriptAnalyzer

All issues in PowerShell/PSScriptAnalyzer

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.