#psscriptanalyzer search results
New #PSScriptAnalyzer release today 🥳 Release 1.24.0 · PowerShell/PSScriptAnalyzer
@PowerShell_Team (@jwtruher and I) have done it again and released a new version of #PSScriptAnalyzer. github.com/PowerShell/PSS…
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)
Spot the difference! Non-working code copied from web page - wrong kind of dash! Doh! That's 2 hours of my evening I'm not getting back. Long time since I've been bitten by this - must run #PSScriptAnalyzer more often! Useful troubleshooting script coming soon.
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…
Docs updates of the #PSScriptAnalyzer 1.21.0 release are now live as well at learn.microsoft.com learn.microsoft.com/en-us/powershe…
#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…
github.com
Release PSScriptAnalyzer v1.21.0 · PowerShell/PSScriptAnalyzer
1.21.0 - 2022-09-14 New Rule Add AvoidMultipleTypeAttributes rule (#1705) (thanks @hankyi95) Add the AvoidSemicolonsAsLineTerminators rule to warn about lines ending with a semicolon. Fix (#824) (...
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…
github.com
Release PSScriptAnalyzer v1.21.0 · PowerShell/PSScriptAnalyzer
1.21.0 - 2022-09-14 New Rule Add AvoidMultipleTypeAttributes rule (#1705) (thanks @hankyi95) Add the AvoidSemicolonsAsLineTerminators rule to warn about lines ending with a semicolon. Fix (#824) (...
⚠️ 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…
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?😆
Ohhh just off the top of my head... VS @Code, @PowerShell_Team (esp #PSScriptAnalyzer), #WindowsTerminal, @dotnet, @typescript, idk if it counts but @github, and OF COURSE @docsmsft!!!!
What open source technology co-created/co-maintained/contributed by Microsoft do you love? #dta #opensource
Something went wrong.
Something went wrong.
United States Trends
- 1. FINALLY DID IT 567K posts
- 2. 60 Minutes 113K posts
- 3. #IDontWantToOverreactBUT N/A
- 4. Greenland 23.9K posts
- 5. #Fliffmas N/A
- 6. Bari Weiss 93.5K posts
- 7. NextNRG Inc. N/A
- 8. The Odyssey 43.1K posts
- 9. #MondayMotivation 33K posts
- 10. Provo N/A
- 11. Bobby Petrino 1,103 posts
- 12. Chris Rea 13.7K posts
- 13. #MondayMorning 1,512 posts
- 14. #HunSen N/A
- 15. Christopher Nolan 44.6K posts
- 16. Victory Monday 2,956 posts
- 17. Happy Holidays 65.1K posts
- 18. Barry Manilow N/A
- 19. Algorhythm Holdings N/A
- 20. Vance 254K posts