A strange idea: why not work using pipeline objects, e.g. in Add-WindowsCapability?
Microsoft is proud that PowerShell works with objects and never gets tired of announcing this wonderful achievement everywhere.
Now I have an apparently extraordinary idea:
Why does M$ not always and mandatory work with the objects, so that commands of the same subject automatically understand each other?
This would allow us commands as we expect it. Without googling for solutions... once more. Such commands must simply work:
Get-WindowsCapability -Online? Name -like' OpenSSH. Client*'. | Add-WindowsCapability
The current M$ "solution" is that very often we have to handle properties and therefore we fall back to the string handling.
Very Annoyoing - does PowerShell really need another 10 years to just follow it's own concepts?
"It just works" should be the principle.