Skip to main content

What is the Difference between $PSItem and $PSItem.Something?

Diversity is a wonderful thing.  So many different experiences leads us to look at the same thing in so many different ways.  I just had a simple, yet really good question in my PowerShell class.
“What is the difference between $PSItem and $PSItem.something?”

Good question.  We are currently studying the PowerShell Pipeline.  As a result, we are looking at $_ and $PSItem.  These two automatic variables represent the current object in the PowerShell pipeline.  If you look at the PowerShell help file About_Automatic_Variables you will see this:
    $_
       Same as $PSItem. Contains the current object in the pipeline object.
       You can use this variable in commands that perform an action on every
       object or on selected objects in a pipeline.

I tend to use $_ because it is shorter and most of my content needs to fit nicely in a book or in a blog post.  Let’s look at an object that we will place in the PowerShell pipeline.
PS Variable:\> Get-Date | Get-Member -MemberType Properties


   TypeName: System.DateTime

Name        MemberType     Definition                                                                 ----        ----------     ----------                                                               DisplayHint NoteProperty   DisplayHintType DisplayHint=DateTime                                     Date        Property       datetime Date {get;}                                                       Day         Property       int Day {get;}                                                           DayOfWeek   Property       System.DayOfWeek DayOfWeek {get;}                                         DayOfYear   Property       int DayOfYear {get;}                                                     Hour        Property       int Hour {get;}                                                           Kind        Property       System.DateTimeKind Kind {get;}                                           Millisecond Property       int Millisecond {get;}                                                   Minute      Property       int Minute {get;}                                                         Month       Property       int Month {get;}                                                         Second      Property       int Second {get;}                                                         Ticks       Property       long Ticks {get;}                                                         TimeOfDay   Property       timespan TimeOfDay {get;}                                                 Year        Property       int Year {get;}                                                           DateTime    ScriptProperty System.Object DateTime {get=if ((& { Set-StrictMode -Version 1; $this.DisplayHint }) -ieq  "Date")...    

This object has several members.  This first example will show you the results of using just $PSItem
PS C:\> Get-Date | ForEach-Object { $PSItem }

Tuesday, July 12, 2016 1:15:22 PM

This second example will show you the result of using $PSItem.DayOfYear
PS C:\> Get-Date | ForEach-Object { $PSItem.DayOfYear }
194

This third example involves a method of the object.
PS Variable:\> Get-Date | ForEach-Object { $PSItem.AddDays(10) }

Friday, July 22, 2016 2:59:56 PM

See the difference?  When you reference $PSItem, you are referencing the entire object.  When you add the name of a property or the name of a method of the object to $PSItem, you are asking for the value of that property or for that method to execute.



Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

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.

How to run GPResult on a remote client with PowerShell

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.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the