Problem
You want to prevent PowerShell from interpreting special characters or variable names inside a string.
Solution
Use a non-expanding string to have PowerShell interpret your string exactly as entered. A nonexpanding uses the single quote character around its text.
PS >$myString = 'Useful PowerShell characters include: $, `, " and { }' PS >$myString Useful PowerShell characters include: $, `, " and { }
If you want to include newline characters as well, use a nonexpanding here string, as in Example 52.
Example 52. A nonexpanding here string that includes newline characters
PS >$myString = @' >> Tip of the Day >> >> Useful PowerShell characters include: $, `, ', " and { } >> '@ >> PS >$myString Tip of the Day
Useful PowerShell characters include: $, `, ', " and { }
Discussion
In a literal string, all the text between the single quotes becomes part of your string. This is in contrast to an expanding string, where PowerShell expands variable names (such as $myString) and escape sequences (such as `n) with their values (such as the content of $myString and the newline character).
Nonexpanding strings are a useful way to manage files and folders that contain special characters that might otherwise be interpreted as escape sequences.
“Create a String, ” one exception to the “all text in a literal string is literal” rule comes from the quote characters themselves. In either type of string, PowerShell let you place two of that string’s quote characters together to include the quote character itself:
$myString = "This string includes ""double quotes"" because it combined quote characters." $myString = 'This string includes ''single quotes'' because it combined quote characters.'
If you need dedicated infrastructure for Windows applications and PowerShell workloads, consider a United Kingdom Dedicated Server for greater control over scripting, automation, system configuration, and server resources.