Add ability to determine when script uses language features and/or cmdlets not available in the specified minimum version of PowerShell

This is increasingly becoming an issue as PowerShell gets new language features and cmdlets. And cmdlets get new parameters, etc. I could have a #requires -version 3.0 in my script but I'm developing on PowerShell 5.0. It is real easy to slip up and use a lang feature ("using namespace System.Diagnostics") or a cmdlet (New-TemporaryFile) or a new cmdlet parameter (PassThru added to Enable-JobTrigger in v4). It would be great if ScriptAnalyzer saw a #requires -Version X.0 and warned (or errored) when I used a feature not available on X.0. Likewise, I would like to have a parameter to ScriptAnalyzer where I could tell it the minimum version I want to target (perhaps I have several scripts written at different times that have varying levels of #requires -Version).

For bonus points, if someone specified neither the command line parameter (MinimumPowerShellVersion) or had any #requires or min version in their PSD1 file, it would be nice if ScriptAnalyzer told me that - "Scripts require at least version 4 due use of -PassThru parameter on Enable-JobTrigger and use of Get-FileHash cmdlet).

Where things get a bit more tricky is setting a minimum Windows OS version. But the need is there since I have a whole bunch of cmdlets available to me on Windows 8.1 that I know are not available on Windows 7.

Inizia esaminando l’entry point di ScriptAnalyzer e il modo in cui attualmente gestisce le dichiarazioni #requires, l’uso dei cmdlet, le funzionalità del linguaggio e i parametri. Confronta le origini richieste per la versione minima—l’input dalla riga di comando, #requires e i metadati PSD1—e definisci come gli avvisi debbano identificare le funzionalità non supportate, incluso il caso della versione di Windows. Il lavoro è completato quando l’ambito e le regole di compatibilità sono specificati abbastanza dettagliatamente da consentire l’aggiunta di test mirati per l’analizzatore.