Ability to bind concerned PowerShell version to a rule

It might be helpful that in the case a rule only applies to a specific (minimum) PowerShell versions as for e.g.:

• AvoidUsingWMICmdlet

And new request/issues:

• UseCompatibleStrings
• UseCompatibleSyntax
• AvoidNewObjectCmdlet

to have the possibility to add that (minimum) PowerShell version (e.g. MininumPowerShellVersion) to that rule.

Meaning e.g. the AvoidUsingWMICmdlet rule might have MininumPowerShellVersion set to 3.0
This would add the possibility for two additional features:

• Suppressing the specific rule by using the #Requires -Version x.x statement.
  E.g.:
  • adding #Requires -Version 2.0 would suppress the AvoidUsingWMICmdlet rule
  • adding #Requires -Version 7.0 would allow the use of `e (suppress the proposed UseCompatibleStrings rule)
• A general UseRequiresStatement rule when a rule with a minimal version applies and the #Requires -Version x.x is not set (or set incorrectly)
  E.g. if any of the rules applies, it generate a warning that the #Requires -Version x.x statement should be set.

Commencez par lire la documentation de la règle AvoidUsingWMICmdlet et les issues associés UseCompatibleStrings, UseCompatibleSyntax et AvoidNewObjectCmdlet. Examinez ensuite la manière dont les règles sont représentées et dont #Requires -Version est géré. Le travail est terminé lorsque le comportement proposé pour la version minimale, la suppression et le comportement de UseRequiresStatement ont un périmètre d’implémentation défini.