Skip to main content

When to use Single and Double quotes with PowerShell

By

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.

Labels:

Comments

Post a Comment

Popular posts from this blog

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Post a Comment
Read more

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

Backup and Restore AD LDS with DSDBUTIL.exe

By
Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...
6 comments
Read more