Hi all,

I'm trying to write a standard text log file of some file copy operations. I need to build the string complete during runtime, then output the string to a file (backing up a server, don't want to write the log to disk until all files are processed).

I tried using both \n and \r characters when building my string, and my output is sort of correct: when viewed in Notepad, there's no line breaks. When viewed in Notepad++, the line break format is exactly as intended.

Not a big deal, I use Notepad++ anyway, but curious why it's not outputting correctly in Notepad?

Thanks,

ex. notepad.exe


same file in notepad++


When I copy from Notepad and paste here in UA, the line breaks show.

I guess my question is: why isn't notepad displaying the line breaks?

Thanks,

>> I tried using both \n and \r characters when building my string <<

Have you combined them?

strMystring = "Hello\r\nWorld"

Or ... have you tried Environment.NewLine?

strMystring = "Hello" + Environment.NewLine + "World"

I think I tried the combo: \r\n but it did this:



I'll try Environment.NewLine but I won't see the results until tomorrow.

>> I think I tried the combo: \r\n but it did this: <<

Did it show dbl-spacing in Notepad or Notepad++ ?

The reason I ask is that Notepad++ is likely to be more "browser-ish" and do well with UNICODE and thus only need \n (or an \r -- can't remember which), where as Notepad is more suited to ASCII encoding (IIRC).

How are you creating your text file? There are so many ways and I am wondering whether you are creating your text file as UNICODE text file or an ASCII text file, thus causing the different presentation to the user with different applications.

----

Have you tried to view the file in WordPad?

>> Did it show dbl-spacing in Notepad or Notepad++ ? <<

I'd have to try again but I think maybe Notepad++



>> only need \n (or an \r -- can't remember which), <<

Either one, or both - the view is the same in Notepad++



>> How are you creating your text file? <<




>> Have you tried to view the file in WordPad? <<

I haven't. I'll check that too when I get back into it.


For all practical purposes, the log is fine, I don't necessarily need to change it, but the more I know the "why" the better off I'll be later down the road. It might be a bit before I dig back into it fully (on to other projects) but I'll definately keep the suggestions on hand.

Thanks!

StreamWriter() defaults to UTF-8 encoding (IIRC), but Notepad likes ASCII, and Notepad++ can likely compensate for either encoding. I know your log is not "broken", but you may want to investigate using the File class (which is static) ...



WriteAllText creates/overwrites the file, writes the data, then closes the file.

---

If you want to keep your code as it is and still use the StreamWriter, you can still specify the encoding ...




Hope this helps!

I didn't know we could write with the File class. Looks handy, I'll check it out.

Thanks!

(IMG:style_emoticons/default/thumbup.gif)

Hi Brent,

Looks like Encoding.ASCII did the trick. Of additional note, it's "\r\n" rather than one or the other, according to this statement from the Environment.NewLine MSDN Documentation:



Thanks for the direction - seems to be squared away.