Explain pipeline members
Documentation: Microsoft Learn
Get-Process emits its objects and Get-Member consumes them, reporting the type name once and then every property, method, and property set that type exposes.
The script
Script reader
Inspect before you run
Inspect the script below. It does not run in this browser.
Inspection only — no command has run.
Show reference output
See the objects move
Inspect this authored example with fictional data in the bounded browser model. The numbered stages show how its objects change.
Get-Process | Get-Member- Stage 1Get-Process
Positional values or no named parameters - Stage 2Get-Member
Positional values or no named parameters
How it works
Get-Process emits its objects and Get-Member consumes them, reporting the type name once and then every property, method, and property set that type exposes. The output describes the shape of the object rather than the values in it.
Adapting it
Add -MemberType Property to strip the methods out when you are hunting for something to select on, and -Name with a wildcard to find a property whose name you only half remember.
If the result is unexpected
Get-Member shows a different type than the one expected downstream.
Formatting, property expansion or array enumeration can change what reaches the pipeline.
- Inspect the object immediately before the failing stage and compare type and property names.
Validate the result
The downstream command receives the expected object type and required properties.
Keep the check reliable
Keep inspection near pipeline boundaries and format only for final display.