Why exclude PropertieSet from Properties?

[System.Management.Automation.PSmemberTypes]:roperties -band
[System.Management.Automation.PSmemberTypes]:ropertyset

The above expression returns false which means that

Get-Process | Get-Member -MemberType Properties

will not return the PropertySet property associated with
System.Diagnositic.Process

The same applies to MemberSets and Methods even though at least I read
Methods to include MemberSets likewise with Properties.

These appear to be a conscious effort on the PS team but I don't understand
their reasoning.

http://msdn2.microsoft.com/en-us/lib...mbertypes.aspx

Personal opinion?

It allows users to get the member types they want (and only the member types
they want).

With the current implementation I can do this:

Get-Process | Get-Member -MemberType Property,PropertySet

or

Get-Process | Get-Member -MemberType Property

or

Get-Process | Get-Member -MemberType PropertySet

Similarly if I want to get just note properties, I can do this:

Get-Process | Get-Member -MemberType NoteProperty

If Property gave me PropertySet types as well, I'd have to use a
Where-Object call in the pipeline to filter them out.

Why would you want to get property sets at the same time that you are
getting properties?

--
Kirk Munro [MVP]
Poshoholic
http://poshoholic.com


"Bob Landau" <BobLandau@xxxxxx> wrote in message
news:AB24A049-6160-4B32-87A1-106B94F4EE3F@xxxxxx

It's surprising that many parameters on many cmdlets actually take
arrays, rather than the single items that we usually put in. A lot of
hidden power.

-Karl