Need understanding as to why string.StartsWith() is true when it should be false

Question

So I have this file that I download via ftp. The file is just a config file for a system at my company I work for. Once the file is downloaded I open the file and processor the file. Part of the processing of the file is to check to see if a line starts with a Unicode character \u001a.

This is where I am stumped because .StartsWith("\u001a") is always true, yet I cannot see why. If I view the file in Notepad++ or in a hex editor, I just don't see that.

So there is something I am missing here.

Here's a minimal example (fiddle):

// prints True in .NET 5 Console.WriteLine("Hello".StartsWith("\u001a"));

Comments are not for extended discussion; this conversation has been moved to chat. — Samuel Liew
– Samuel Liew, Commented Sep 26, 2021 at 9:31

2 revs · Accepted Answer · 2021-09-28 12:52:40Z

It's because a breaking change in the globalizations APIs in .NET 5. You can choose one of the following approaches

Use StringComparison.Ordinal or OrdinalIgnoreCase
Use NLS instead of ICU, with one of the following ways:

In the project file:

<ItemGroup> <RuntimeHostConfigurationOption Include="System.Globalization.UseNls" Value="true" /> </ItemGroup>

In the runtimeconfig.json file:

{ "runtimeOptions": { "configProperties": { "System.Globalization.UseNls": true } } }

By setting the environment variable DOTNET_SYSTEM_GLOBALIZATION_USENLS to the value true or 1.

Collectives™ on Stack Overflow

Need understanding as to why string.StartsWith() is true when it should be false

1 Answer 1

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Linked

Related