Difference between "\n" and Environment.NewLine

Question

What is the difference between two, if any (with respect to .Net)?

anthony · Accepted Answer · 2009-06-19T00:29:38.747

231

Depends on the platform. On Windows it is actually "\r\n".

From MSDN:

A string containing "\r\n" for non-Unix platforms, or a string containing "\n" for Unix platforms.

edited Jun 19 '09 at 00:29

answered Jun 18 '09 at 23:46

anthony

40,424
5
55
128

5

Which UNIX platform does .NET run to Microsoft put into its doc? (I mean, a part from Mono.) – Jack Jul 27 '14 at 04:24
13

@Jack You could be writing to a file that will be opened in Unix platform. Or sending text in package that will be received by a unix platform. And in a few months .net will be running on Unix platforms. It already has begun – John Demetriou May 01 '15 at 13:36
So just for clarity: on a non-Unix platform `Environment.NewLine` is `\r\n` but `\n` is also called "new line". Why didn't they just call the latter by its more well-known name "line feed" and cut out the confusion? They could have used `\l` also. – rory.ap Sep 26 '18 at 15:52

aloisdg · Answer 2 · 2017-06-22T12:41:02.020

Exact implementation of Environment.NewLine from the source code:

The implementation in .NET 4.6.1:

/*===================================NewLine====================================
**Action: A property which returns the appropriate newline string for the given
**        platform.
**Returns: \r\n on Win32.
**Arguments: None.
**Exceptions: None.
==============================================================================*/
public static String NewLine {
    get {
        Contract.Ensures(Contract.Result<String>() != null);
        return "\r\n";
    }
}

source

The implementation in .NET Core:

/*===================================NewLine====================================
**Action: A property which returns the appropriate newline string for the
**        given platform.
**Returns: \r\n on Win32.
**Arguments: None.
**Exceptions: None.
==============================================================================*/
public static String NewLine {
    get {
        Contract.Ensures(Contract.Result() != null);
#if !PLATFORM_UNIX
        return "\r\n";
#else
        return "\n";
#endif // !PLATFORM_UNIX
    }
}

source (in System.Private.CoreLib)

public static string NewLine => "\r\n";

source (in System.Runtime.Extensions)

yeah :) For some reason I was expecting the .NET implementation to be some huge complicated function — brettwhiteman, Aug 25 '15 at 04:35
Considering the simplicity of the source in this instance, it probably should be the answer. — Chris Walter, Jan 04 '16 at 21:22

score 70 · Answer 3 · answered Jun 19 '09 at 00:14

70

As others have mentioned, Environment.NewLine returns a platform-specific string for beginning a new line, which should be:

"\r\n" (\u000D\u000A) for Windows
"\n" (\u000A) for Unix
"\r" (\u000D) for Mac (if such implementation existed)

Note that when writing to the console, Environment.NewLine is not strictly necessary. The console stream will translate "\n" to the appropriate new-line sequence, if necessary.

answered Jun 19 '09 at 00:14

P Daddy

28,912
9
68
92

The Mac implementation does exist. Just Mono. Runs on anything. – Dykam Jan 17 '10 at 07:41
28

Just a note, that would be old macs; new (OSX) macs use `\n` – BlueRaja - Danny Pflughoeft Jun 04 '11 at 22:47
2

@Dykam, yeah but it runs real slow-like on my HP48gx – cod3monk3y Feb 04 '14 at 16:09
@cod3monk3y: That's fast compared to my HP48sx! – awe Feb 10 '14 at 08:48
1

As others have mentioned and as is visible in the .Net source also attached to this question, this answer is not correct. – Chris Walter Jan 04 '16 at 21:23
@ChrisWalter this answer could be correct back in 2009. Today, it is outdated. – aloisdg Sep 14 '17 at 11:47
@aloisdg 2009? Apple hasn't used CR for 17 years; not since the initial release of macOS. This "non-Unix" thing is misleading. Windows is the only relevant OS that doesn't use LF. Linux, macOS, the BSDs, BeOS, RISC OS, and many more all use LFs. – Blieque Jul 20 '18 at 10:13
2

@Blieque just saying that it might have been true in 2009, not that it was. I didnt check. – aloisdg Jul 20 '18 at 12:08

score 27 · Answer 4 · edited May 03 '16 at 09:00

27

Environment.NewLine will return the newline character for the corresponding platform in which your code is running

you will find this very useful when you deploy your code in linux on the Mono framework

edited May 03 '16 at 09:00

George G

7,443
12
45
59

answered Jun 18 '09 at 23:50

Rony

9,331
2
22
22

score 8 · Answer 5 · answered Jun 18 '09 at 23:47

8

From the docs ...

A string containing "\r\n" for non-Unix platforms, or a string containing "\n" for Unix platforms.

answered Jun 18 '09 at 23:47

JP Alioto

44,864
6
88
112

score 5 · Answer 6 · answered Jun 19 '09 at 13:35

5

You might get into trouble when you try to display multi-line message separated with "\r\n".

It is always a good practice to do things in a standard way, and use Environment.NewLine

answered Jun 19 '09 at 13:35

Yahya

3,386
3
22
40

score 4 · Answer 7 · answered Jun 18 '09 at 23:47

4

Environment.NewLine will give "\r\n" when run on Windows. If you are generating strings for Unix based environments, you don't want the "\r".

answered Jun 18 '09 at 23:47

Jeff Meatball Yang

37,839
27
91
125

Difference between "\n" and Environment.NewLine

7 Answers7

Linked

Related