Replies: 2 comments
-
Hi, I don't see any ValueFromPipeline or similar attributes on any of the parameters so I assume PowerShell does not know what to do with the input pipeline. It has to populate one of the parameters for ProcessRecord() to find it. Although it may fail to start, it did not start to fail, or did it previously work and this is a change in behaviour, or just expectations? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Although it may fail to start, it did not start to fail, or did it previously work and this is a change in behaviour, or just expectations? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In writing https://stackoverflow.com/questions/78392559/how-to-create-a-windows-control-panel-window-using-clsid-in-powershell , I arrived at this snippet:
Note that the "usual", non-piped command:
... works fine, and starts the (Control Panel) Network Connection windows.
Why does piping CLSID to
start
fail?Beta Was this translation helpful? Give feedback.
All reactions