Use `StaticParameterBinder` for `AvoidDeprecatedCommands`

[iRon7]

Thanks for sharing your rules.
Our company is preparing to move to PowerShell 7 as well (I got your name from a college that met you in Malmo).
I was about to write a similar rule with a configuration list as you did for AvoidDeprecatedCommands but I am now considering to just use yours.
Anyways, at the moment I have several individual rules to avoid specific commands myself and with that wanted to better resolve the command and it parameters. Fyi, there is in fact a .net automation StaticParameterBinder.BindCommand class to resolve the command line, see: https://stackoverflow.com/a/79634016/1701026

Maybe something you might want to use for the concerned AvoidDeprecatedCommands rule...

[israem]

Hey

Thanks for raising this.

Great suggestion, we were a little apprehensive about using the parameter binder here due to performance concerns (we use it in other rules but just to generate corrections). The performance concern are because the engine needs to resolve the command. If it doesn't, we may only get position-based parameters.

However, looking at this rule again, we would only need the binder for 3-4 commands, only ones where we restrict specific parameters. Additionally, all of those commands are probably already loaded since they're are built -in so it should be pretty safe to use it.

We'll consider your suggestion and update the rule if needed.

[iRon7]

Just fyi: with regards to avoiding the Out-File cmdlet, I am about to release this WindowsOutFilePatch module in our environment which contains a replacement for the Out-File cmdlet in Windows PowerShell that supports the normally PowerShell 7-only utf8BOM and utf8NoBOM -Encoding specifiers, for cross-edition consistency; you can install it with, e.g.,
Install-Module WindowsOutFilePatch -AllowClobber -Scope CurrentUser and then use Out-File -Encoding utf8NoBOM in Windows PowerShell too.