Skip to main content

When to use Single and Double quotes with PowerShell

Here is another one of those enduring questions from my PowerShell classes. When to use single and double quotes.

First off we need to establish the object type that is created by both single and double quotes. Take a look at the code below. Both single and double quotes produce a System.String object type. At this point there is no difference between the two.

PS C:\> $Single = ''

 

PS C:\> $Double = ""

 

PS C:\> $Single.GetType()

 

IsPublic IsSerial Name                                     BaseType                                         

-------- -------- ----                                     --------                                         

True     True     String                                   System.Object                                    

 

 

 

PS C:\> $Double.GetType()

 

IsPublic IsSerial Name                                     BaseType                                         

-------- -------- ----                                     --------                                         

True     True     String                                   System.Object 

The difference comes when you create strings that contain variables.

PS C:\> $Var1 = "Hello"

 

PS C:\> $Var2 = 'World'

 

PS C:\> Write-Output "$Var1 $Var2"

Hello World

 

PS C:\> Write-Output '$Var1 $Var2'

$Var1 $Var2

Here two strings are produce from variables. The first utilizes double quotes while the second utilizes single quotes. In the first, the value of the variables are placed in the string. In the second string, utilizing single quotes, the characters are treated as literal. In other words, they are no longer treated as variable names.

You may be thinking “Big deal”. Well, here is where it can become a big deal. Consider the following.

PS C:\> Write-Output 'The price of gas is $4.35 a gallon.'

The price of gas is $4.35 a gallon.

 

PS C:\> Write-Output "The price of gas is $4.35 a gallon."

The price of gas is .35 a gallon.

Do you see the difference? In the string created with single quotes, you get accurate output. In the other string, PowerShell is looking for the value of the variable $4. Well, $4 has a value of NULL. Now you just set the price of gas at $.35 a gallon. We call this a RGE. Otherwise known as a Resume Generating Event.

You could write your string this way.

PS C:\> Write-Output "The price of gas is `$4.35 a gallon."

The price of gas is $4.35 a gallon.

What you may not see is in front of the “$” is a “`” back tick. This is the PowerShell Escape Character. Be careful if you use it. It is hard to see. The Escape Character makes the dollar sign be treated as a character instead of the name of a variable. This will give us the correct output. Remember, this is not the single quote, but the back tick.  The back tick is on the left of a US keyboard where the single quote is on the right.

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.