Store string variable in text file

Question

I want to create a (blank) file, and optionally store a text message in it. This is my code for doing so:

$null = new-item "$filename" -type file
write-output ("Message: <<$message>>")
if ( -not ($message= "")) {
    Add-Content "$filename" "Message: <$message>"
}

The 1st line creates the file. This works. The 2nd line visually verifies that I do in fact supply a string (say, the proverbial "hello world"). The 3rd line evaluates to $true and does execute its nested block. But the 4th line stores a message saying: Message: <>.

I can't figure out the proper syntax for passing the actual value from $message. Help?

arco444 · Accepted Answer · 2015-11-23 12:00:38Z

3

You're using the wrong operator for comparing the $message value. See Get-Help about_comparison_operators.

By saying if ( -not ($message= "")), you actually set the value of $message to be an empty string.

Instead, use -eq, -ne or simply just test it:

# Option 1
if ( -not ($message -eq "")) {
    Add-Content "$filename" "Message: <$message>"
}
#Option 2
if ($message -ne "") {
    Add-Content "$filename" "Message: <$message>"
}
#Option 3
if ($message) {
    Add-Content "$filename" "Message: <$message>"
}

answered Nov 23, 2015 at 12:00

arco444

23k12 gold badges66 silver badges67 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

KlaymenDK Over a year ago

Excellent, that fixed it. You probably guessed that I'm new to PS, and the syntax sometimes still seems quite round-about.

Χpẘ Over a year ago

@KlaymenDK Here's some really different syntax for you: ${c:\temp\afile.txt} = "content to write to file with an assignment statement". This unusual syntax is due to PS' support of providers (help about_providers).

Collectives™ on Stack Overflow

Store string variable in text file

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related