Windows PowerShell Blog - ScriptAnalyzer in GitHub and availability on Powershell Gallery

The Windows PowerShell Blog ^ | Apr 29, 2015 | PowerShell Team

[dayglored]

Windows PowerShell Blog

"Automating the world one-liner at a time…"

With the release of Windows Management Framework 5.0 April Preview, we are excited to announce that PowerShell ScriptAnalyzer development has moved to GitHub for greater collaboration & community involvement.

https://github.com/PowerShell/PSScriptAnalyzer

Also, we have published v1.0 of ScriptAnalyzer to PSGallery.

https://www.powershellgallery.com/packages/PSScriptAnalyzer/

Here are the significant changes in this release:

Features:

• "Recursive" switch to analyze a folderpath in Invoke-ScriptAnalyzer
• Three levels of Severity - Error/Warning/Informational
• Robust Engine that does emits non-terminating errors (Ex: for failed ast parse) and continues rule application when running on multiple scripts
• Add wild card supports for rules in Invoke-ScriptAnalyzer and Get-ScriptAnalyzerRule. Eg. Invoke-ScriptAnalyzer -IncludeRule PSAvoid* will apply all rules starting with PSAvoid* in built in rule assemblies.
• Add -Severity to Get-ScriptAnalyzerRules. Get-ScriptAnalyzer -Severity will filter rules based on the severity given.
• Suppression functionality. Users are now able to specify suppression on certain parts of the scripts by specifying "SupressMessageAttribute". Also comes with this feature is the ability for users to display a list of suppressed messages.

More including Rules, Fixes on the MSDN Blog page...

[dayglored]

Microsoft has open-sourced the development of the PowerShell ScriptAnalyzer, moving it to GitHub to make it more readily available. This is great news for programmers and others who work in or with Windows PowerShell.

[dayglored]

Here's one for the Windows programmers ... PING!

You can find all the Windows Ping list threads with FR search: search on keyword "windowspinglist".

Thanks to tacticalogic for the heads-up!

[Scutter]

I’ll have to check this out. I love PowerShell - great scripting language.

[miliantnutcase]

Thanks for this!

[rarestia]

*goes to GitHub*

Ooooh... shiny. Will report back on new functionality. Got us scripting nerds all in a tizzy.

Unrelated, wish me luck. I take my final exam for my Server 2012 MCSA on Friday.

[no-s]

Microsoft has open-sourced the development of the PowerShell ScriptAnalyzer

Oooooh...shiny. Can we just use Lisp or Scheme instead? I script in PowerShell daily and frankly I'm sick of bizarre irregular syntax and constantly having to coerce strange objects with strange side effects and behaviors into doing my bidding. Probably only 25% of Powershell makes sense, the rest is just vapid "Feeeechurrs" added for the weak-minded. It's like the worst of Perl and Python mixed together. I'm constantly discovering Windows Devops and Sysadmins sneaking in Node servers (OMG you can get it from NuGet) just so they can have some luck GSD in provisioning.

Whew. I didn't realize I had a rant waiting for this...at least I'm not pining for CMS and EXEC and REXX any more...

[tacticalogic]

I script in PowerShell daily and frankly I'm sick of bizarre irregular syntax and constantly having to coerce strange objects with strange side effects and behaviors into doing my bidding.

If you hate it so much, why are you using it daily? I don't think there's anything you can do in a half-dozen line of PS code that couldn't be done just as well with a few hundred lines of VB.

[dayglored]

> I don't think there's anything you can do in a half-dozen line of PS code that couldn't be done just as well with a few hundred lines of VB.

VB LOL ;-)

[zeugma]

at least I'm not pining for CMS and EXEC and REXX any more...

Back when OS/2 was big, I thought it was the best thing since sliced bread. I actually had an entire communications program written in nothing but REXX.

 

[tacticalogic]

Back when OS/2 was big, I thought it was the best thing since sliced bread. I actually had an entire communications program written in nothing but REXX.

I remember NT4 shipped with the Regina REXX interpreter.

[zeugma]

I remember NT4 shipped with the Regina REXX interpreter.

I think the first time I saw REXX was in IBMDOS 7 (might have been IBMDOS 6. I was astounded. A real freaking scripting language in DOS. was a rocking advantage, back then. It put 'bat' files to ugly shame. Since that time, it is only with MS Powershell that Microsoft has finally developed a decent tool for scripting.

[tacticalogic]

IBMDOS 7

IIRC, that was called PC DOS 7. And also came with a copy of Stacker.

[no-s]

If you hate it so much, why are you using it daily?

heheh...because most of the time getting Windows stuff done requires using what Microsoft gave you to do it with, however inferior the solution is. Just an example, my Tier-1 staff got all excited about Circonus for some reason, they're into it like toddlers into cotton candy. Under the integration sugar is Node.js calling windows command line stuff. Who writes the Windows command line stuff? Yours truly - in powershell. This is actually an improvement over the previous Nagios integration - that was written by some name-withheld-to-protect-the-guilty ex-Hotmail DBA who cloned his exemplar VBscript a few thousand times and said "see how easy that was?"

[tacticalogic]

I can understand how you might not like the opportunistic typecasting it does if you’re used to strictly typed languages. But I came to PowerShell through Exchange, so I’m kind of the “OPS” side of it. I had to get past the whole dotnet / object-oriented programming curve from being used to command line utilities.

[zeugma]

IIRC, that was called PC DOS 7. And also came with a copy of Stacker.

Yup. That was it. I wish IBM had been able to market itself out of a paper bag at the time.

[tacticalogic]

I wish IBM had been able to market itself out of a paper bag at the time.

IMHO, they screwed the pooch with Micro Channel Architecture.