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

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

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