Vista - Get-Member -InputObject returns generic data; bug?

If I do this:

Get-Command | Get-Member

I get back members of CmdletInfo objects. However, if I do this:
$gcm = Get-Command; Get-Member -InputObject $gcm
or this:
Get-Member -InputObject $(Get-Command)
I get back System.Object[] information.

From my understanding of InputObject, behavior should be the same whether I
am piping objects in or supplying them via InputObject. Is this a bug?

This behavior is by design.
We don't unravel InputObject, therefore you are applying get-member on an
array of CmdletInfo objects when you do "Get-Member -InputObject $gcm".
While in the pipeline scenario, you are applying get-member on each
individual CmdletInfo object.

--
Wei Wu [MSFT]
Windows PowerShell Team
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.


"Alex K. Angelopoulos [MVP]" <a k a @ m v p s . o r g> wrote in message
news:eXX7aVGlGHA.4828@TK2MSFTNGP04.phx.gbl...
> If I do this:
>
> Get-Command | Get-Member
>
> I get back members of CmdletInfo objects. However, if I do this:
> $gcm = Get-Command; Get-Member -InputObject $gcm
> or this:
> Get-Member -InputObject $(Get-Command)
> I get back System.Object[] information.
>
> From my understanding of InputObject, behavior should be the same whether
> I am piping objects in or supplying them via InputObject. Is this a bug?
>
>
>

OK. And I can actually use that behavior.

"Wei Wu [MSFT]" <wwu@microsoft.com> wrote in message
news:erzQbjIlGHA.3776@TK2MSFTNGP03.phx.gbl...
> This behavior is by design.
> We don't unravel InputObject, therefore you are applying get-member on an
> array of CmdletInfo objects when you do "Get-Member -InputObject $gcm".
> While in the pipeline scenario, you are applying get-member on each
> individual CmdletInfo object.
>
> --
> Wei Wu [MSFT]
> Windows PowerShell Team
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "Alex K. Angelopoulos [MVP]" <a k a @ m v p s . o r g> wrote in message
> news:eXX7aVGlGHA.4828@TK2MSFTNGP04.phx.gbl...
>> If I do this:
>>
>> Get-Command | Get-Member
>>
>> I get back members of CmdletInfo objects. However, if I do this:
>> $gcm = Get-Command; Get-Member -InputObject $gcm
>> or this:
>> Get-Member -InputObject $(Get-Command)
>> I get back System.Object[] information.
>>
>> From my understanding of InputObject, behavior should be the same whether
>> I am piping objects in or supplying them via InputObject. Is this a bug?
>>
>>
>>
>
>

"Wei Wu [MSFT]" wrote:

> This behavior is by design.
> We don't unravel InputObject, therefore you are applying get-member on an
> array of CmdletInfo objects when you do "Get-Member -InputObject $gcm".
> While in the pipeline scenario, you are applying get-member on each
> individual CmdletInfo object.

Yeah, at first I got confused by that behavior too, but I think this design
makes sense once you got the difference.
It should be well documented in the online help though, if it isn't already.

--
greetings
dreeschkind