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

Labels:

Comments

Post a Comment

Popular posts from this blog

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

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more