Search results for #PSScriptAnalyzer
New #PSScriptAnalyzer release today 🥳 Release 1.24.0 · PowerShell/PSScriptAnalyzer
🚀 New PSScriptAnalyzer rule! Measure-GraphPermissionScope scans PowerShell scripts to detect unused Microsoft Graph scopes, enforcing the least privilege & better security. 🔎🔐 github.com/HCRitter/PSSA_… #PowerShell #MicrosoftGraph #CyberSecurity #PSScriptAnalyzer
Any one that can help @bielawb out with #PSScriptAnalyzer rules in binary for #PowerShell?
Any one that can help @bielawb out with #PSScriptAnalyzer rules in binary for #PowerShell?
@PowerShell_Team (@jwtruher and I) have done it again and released a new version of #PSScriptAnalyzer. github.com/PowerShell/PSS…
@vethalik @jandedobbeleer About typing in lengthy command names: don't forget #PowerShell supports aliases, so you can type short versions interactively, and use long versions for readability in scripts (and #PSScriptAnalyzer will help you converting from aliases to long versions)
Almost time for my first session at #PSConfEU. Hope to see everyone in room A2 to learn about #psscriptanalyzer and #pester and how to combine them together! #PowerShell #Testing #Conference
Props to the #PsScriptAnalyzer team. There has been a bug in some of my code that I and ISESteriods never spotted. How did I find it? Setting up automation for the deployment of UcmPsTools to the #PsGallery #GreigHatesHowIDoCurlyBraces
#PowerShell #PSScriptAnalyzer PSScriptAnalyzer (PSSA) 1.21.0 has been released bit.ly/3N349QJ
The latest update of the main PowerShell extension for VS-Code runs now on #PSScriptAnalyzer 1.21.0 as well github.com/PowerShell/vsc…
@guyrleech I always thought you are the #PSScriptAnalyzer....
Docs updates of the #PSScriptAnalyzer 1.21.0 release are now live as well at learn.microsoft.com learn.microsoft.com/en-us/powershe…
Docs updates of the #PSScriptAnalyzer 1.21.0 release are now live as well at learn.microsoft.com learn.microsoft.com/en-us/powershe…
New v2022.9.2-preview release of PowerShell extension includes now #PSScriptAnalyzer 1.21.0 and with that a new setting to configure its new formatting rule, which is off by default: powershell.codeFormatting.avoidSemicolonsAsLineTerminators
#PSScriptAnalyzer 1.21.0 been released and published to the @ThePSGallery . Expect a blog on devblogs.microsoft.com/powershell soon. Here are the release notes for now github.com/PowerShell/PSS…
⚠️ Starting with AZ 2.40.0 its entrypoint changed from a batch to a #PowerShell script but this causes #PSScriptAnalyzer to give a PSAvoidUsingPositionalParameters warning. Working on an exclusion for it and hope to include it in a new release soon.
Hey @TylerLeonhardt Do you have a idea how to fix this? I have a feeling it is a #PSScriptAnalyzer rule in #vscode . I would love at least 1 indentation after a " | " with Select-object. I think it makes the code easier to read. No idea where to start. #PowerShell
I made a #PowerShell #PSScriptAnalyzer custom rule that warns you if you have a format command in the middle of your pipeline! Thanks Gainsville PSUG for the idea! @AndrewPlaTech gist.github.com/JustinGrote/0b…
#Github code scanning now supports #PowerShell #PSScriptAnalyzer! github.blog/2021-07-28-new…
@duckgoop @greggZ251 I get that the explicit check is generally considered easier to read, but if we're optimizing for readability, shouldn't it be the other way around? Consider which sounds more natural: "This object is null" "Null is this object" Is #PSScriptAnalyzer optimizing for King James?😆

Christoph Bergmeister @CBergmeister
1K Followers 209 Following 8x Microsoft MVP, PowerShell Enthusiast and PSScriptAnalyzer Community Maintainer. Senior DevOps Manager @Avanade