Skip to main content

Environment.NewLine or "\r\n"

Ma uitam zilele astea peste un cod si am vazut de mai multe ori cod de genul acesta:
string v2 = v1 + "\n";
Scopul la acest cod este de a trece pe o linie noua. Desi functioneaza si este folosit de catre foarte multi dezvoltatori nu este cea mai buna solutie. Pentru a trece la o linie noua cei de la Microsoft au adaugat o propietatea Environment.NewLine. De fapt aceasta este o constanta ce ne returneaza "\r\n" pe Windows.
IL care se genereaza face un call la System.Environment::get_NewLine() care in spate are urmatoarea implementare pentru Windows:
.method public hidebysig specialname static string get_NewLine() cil managed
{
.maxstack 8
L_0000: ldstr "\r\n"
L_0005: ret
}
In functie de platforma NewLine poate sa difere, o implementare pentru UNIX ar contine doar "\n". Desii Environment.NewLine este mult mai clar in cod, nu cred ca se va renunta la "\r\n" deoarece nimeni nu va uita ce inseamna "\r" sau "\n". Pana se va ajunge sa se scrie aplicatii .NET care sa ruleze by default pe mai multe sisteme de operare o sa mai treaca ceva vreme.
Eu prefer si incerc sa folosesc Environment.NewLine, voi ce folositi?

Update:
Un caz cand nu se poate folosii NewLine este cand vrem sa declaram o constanta care sa contina si NewLine:
const string Text = "Hello" + Environment.NewLine + "Word!";
Din cauza ca NewLine este o propietate si nu o contanta linia de cod scrisa mai sus o sa crape.
Daca lucram cu un TextBox o sa ne trezim ca urmatoarea linie de cod nu ne da rezultatul pe care l-am astepta:
errorTextBox.Text = "Error: \n\n\";
Problema este ca TextBox-ul necesita si un CRLF, nu doar LF. In acest caz avem posibilitati:
errorTextBox.Text = "Error: \r\n\r\n\";
sau
errorTextBox.Text = "Error: "+ Environment.NewLine + Environment.NewLine ;

Comments

  1. Intr-adevar, webdings apar pe chrome (e un span style="font-style: italic; font-family: webdings;" acolo)...

    Cam singurul caz in care Environment.NewLine e util ar fi cand aplicatia produce fisiere text care vor fi citite de un human..

    .NET, Silverlight mai precis _ruleaza_ pe un sistem UNIX-like, si nu ma refer la Mono, ci la Silverlight pe MacOSX, care tot un nepot al BSD Unix e..
    Ce-i drept, ma astept ca orice text editor modern pe MacOSX sa se descurce cu cele 3 stiluri posibile de newlines.

    Cat depsre unit teste, solutia e aceeasi ca la DateTime.Now - cand ai nevoie musai de asa ceva, o tratezi ca o dependinta externa pentru care apoi se poate crea un stub sau mock.

    ReplyDelete
  2. Un caz cand nu se poate folosii NewLine este cand vrem sa declaram o constanta care sa contina si NewLine:

    const string Text = "Hello" + Environment.NewLine + "Word!";

    Din cauza ca NewLine este o propietate si nu o contanta linia de cod scrisa mai sus o sa crape.

    Daca lucram cu un TextBox o sa ne trezim ca urmatoarea linie de cod nu ne da rezultatul pe care l-am astepta:

    errorTextBox.Text = "Error: \n\n\";

    Problema este ca TextBox-ul necesita si un CRLF, nu doar LF. In acest caz avem posibilitati:

    errorTextBox.Text = "Error: \r\n\r\n\";

    sau

    errorTextBox.Text = "Error: "+ Environment.NewLine + Environment.NewLine ;

    ReplyDelete
  3. E cumva logic: pe Windows si MSDOS nu ne putem baza pe orice soft ca va recunoaste doar un \n, de aceea cel mai safe e \r\n ..

    Din pacate genul asta de control characters sunt o mostenire de pe vremea cand output-ul la programe mergea doar la o imprimanta matriciala si nu existau monitoare - doar in acel context are sens un "carriage return" (deplasarea tamburului cu hartie inapoi la dreapta, dar ramane pe aceeasi linie), respectiv "line feed", avansarea cu o linie, dar ramanerea pe aceeasi coloana.. :)
    Cand s-a trecut la CRT-uri, fiecare a interpretat aceste doua caractere cum a crezut ca e mai "logic"..

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too