Thomas Nieto

They don't necessarily have to update scripts because the PowerShel team created the PowerShellCompat module which creates a compatability layer with the existing cmdlet names.

Furthermore NuGet which PowerShellGet leverages for its package management capabilities, does not require any search filtering when querying the public repository. Why make this requirement on PowerShellGet when NuGet can...

I normalized the messages so it would be consistent between module landing page and cmdlet help files. I picked the cmdlet help file description placeholder since it was used more...

I don't know what changed since the original posting but there seems to be new behavior and it can now bind to named parameters. ```powershell PS C:\> Get-Command -foo -bar...

This is due to the PowerShell team migrating the docs from the help xml to about topics. I don't agree with the change but its still there technically but breaks...

@SteveL-MSFT does MS sign any of their HelpInfo xml files or is it just the CAB files?

@sdwheeler do you know what the recommendation is for signing help files? Is it just the cab files or also including the helpinfo xml files?

@sdwheeler I just tried using `Set-AuthenticodeSignature` on the maml help and helpinfo.xml and it failed. You can sign the help cab file. It doesn't look like you can catalog sign...

Is this still a problem? `Update-Help` seems to put files in `~\Documents\PowerShell\Help` now.

Duplicate of #13550