Skip to main content

New Way to add Note Properties with PowerShell V3

For those of you who have taken my PowerShell V2 class probably remember the step-by-step exercise that I took you through to help you build a custom object.  In PowerShell V3, we can create a new NoteProperty with a smaller amount of code.  Below is code that creates an object with a single note property.
$Obj = New-Object -TypeName PSObject
$Obj | Add-Member -MemberType NoteProperty -Name "Value1" -Value 10
Using the Add-Member cmdlet, we declare the member type that we are adding “NoteProperty”. Then we provide it with a name and a value.  In PowerShell V3, two new parameters were added to the Add-Member cmdlet.  They are –NotePropertyName and –NotePropertyValue.  Below is the same object created with this new method.
$Obj = New-Object -TypeName PSObject
$Obj | Add-Member -NotePropertyName "Value1" -NotePropertyValue 10
If your code will be running on clients or servers using PowerShell V2, do not use this new method.  Take a look at the screen shot below.
image
You can see that the script successfully executes in PowerShell V3.  When I switch the shell to the V2 engine and then executed the code, PowerShell V2 hit a run time error because its version of Add-Member does not have a parameter for ‘NotePropertyName’.
Just one of the little hidden tricks inside of PoSH V3.  As always, code for the lowest level of PowerShell that your code will execute on.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

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.