Skip to main content

How to get the members of a array, and not the members of the objects in the array in PowerShell

By

Let’s start off by explaining the situation by creating an array.

$myArray = 1, 2, 3, 4
If I execute $myArray | Get-Member
I get the member information for the integer objects in the array:

TypeName: System.Int32


 
































Name MemberType Definition
CompareTo Method int …
Equals Method bool …
GetHashCodeMethod int …
GetTypeMethod type GetType …
GetTypeCodeMethod System.TypeCode GetTypeCode() …
ToStringMethod string …


 


However, If I execute $MyArray.count, I get a value of 4.  Where did this count property come from?  By looking at the members above, the count property is not listed.  The Count property can from the object of the array, not the objects contained in the array.  To see the members of the object array, type: 

Get-Member -InputObject $MyArray


This will give you the members of the object of $MyArray.  Below is a listing of what you will receive.


 



Name              MemberType
----              ----------
Count          AliasProperty
Address               Method
Clone                 Method
CopyTo                Method
Equals                Method
Get                   Method
GetEnumerator         Method
GetHashCode           Method
GetLength             Method
GetLongLength         Method
GetLowerBound         Method
GetType               Method
GetUpperBound         Method
GetValue              Method
Initialize            Method
Set                   Method
SetValue              Method
ToString              Method
IsFixedSize         Property
IsReadOnly          Property
IsSynchronized      Property
Length              Property
LongLength          Property
Rank                Property
SyncRoot            Property


 


You can see that there is an aliased property called Count.  It is a alias for the Length property.  Below is an excerpt from the Get-Member help file.


-InputObject <psobject>
    Specifies the object whose members are retrieved.


    Using the InputObject parameter is not the same as piping an object to Get-Member. The differences are as follows:


    -- When you pipe a collection of objects to Get-Member, Get-Member gets the members of the individual objects in the collection, such as the properties of the integers in an array of integers.


    -- When you use InputObject to submit a collection of objects, Get-Member gets the members of the collection, such as the properties of the array in an array of integers.


 


 




Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more