-
When a trailing backslash is added to the end of the path for custom script analyzer rules, the rules are not tested. Example:
Invoke-ScriptAnalyzer -Path C:\tmp\MyScript.ps1 -CustomizedRulePath C:\t…
-
The Profile parameter takes a hash table in a .psd1 text file or a hash table in a variable, but it does not take a hash table as the parameter value.
juneb updated
8 years ago
-
Currently we support only PowerShell v5 but it wouldn't take a great deal of effort to support PowerShell 3 and 4. [PoshTools](github.com/adamdriscoll/poshtools) has accomplished this already so ther…
-
Tested on the latest development build at the moment
https://ci.appveyor.com/project/PowerShell/psscriptanalyzer/build/1.0.423/artifacts
Repro: run PSSA on a script
``` powershell
function Write-X([…
-
So users are able to provide a global suppression file/configuration file, to have a list of rule suppression applied to all files within the script module.
-
One issue I've seen with adopting code analysis / FxCop on an existing, large code base is that the number of warnings and errors can be overwhelming. Additionally, code may be released and managemen…
-
This manifest (some fields omitted)
```
@{
...
ModuleToProcess = 'SplitPipeline.dll'
PowerShellVersion = '2.0'
}
```
causes
```
RuleName Severity FileName…
-
Underscore in file name of ps1 to be analyzed generates an error
Error Message:
Invoke-ScriptAnalyzer .\download_ignite.ps1
Invoke-ScriptAnalyzer : Illegal characters in path.
-
## Repro
Clone https://github.com/TravisEz13/PSScriptAnalyzerExamples.git
open the repo in powershell
Invoke-ScriptAnalyzer [.\pipeExample.ps1](https://github.com/TravisEz13/PSScriptAnalyzerExamples/…
-
When running the command:
```
invoke-scriptanalyzer .\a.ps1 -severity error
```
invoke-scriptanalyzer will throw an ArgumentException.