`dotnet test` fails for Norwegian resources on Ubuntu 20.04

Hi,

Running dotnet test in this example project fails for Norwegian resources on Linux, but works fine on Windows. The tests succeed for French and German. I have noticed that dotnet build only produces a bin/Debug/netcoreapp3.1/no/xUnitCulture.resources.dll output file when running on Windows. Is there anything I’m missing?

Possibly related issues:

• aspnet.core 3.1 application does not use satellite assembly resources like localization of referenced libraries in Linux or docker container
• Satellite assemblies are not produced for registered custom cultures when using .NET Core msbuild
• Resources from Resx ignore current culture when running with xUnit

Thanks, Bjørn

[fjukstad]

Renaming the resource file from Resource.no.resx to Resource.nb.resx results in a nb/ output directory, and makes the tests in the example repository pass on Ubuntu. We can access the resources with CultureInfo("nb") or CultureInfo("nb-NO"). On Windows we do not have to rename the resource file, and we can access the resources with CultureInfo("no"), CultureInfo("nb"), or CultureInfo("nb-NO"). In summary, renaming the resource file and accessing it with nb or nb-NO is a solution, but it would be interesting to know why Resource.no.resx and CultureInfo("no") works on Windows, but not Ubuntu.

[rainersigwald]

I don’t recall a specific fix for no in MSBuild; looking I saw https://github.com/dotnet/msbuild/pull/7853 (match .NET runtime behavior more closely) and https://github.com/dotnet/msbuild/pull/8011 (specific to pseudo-loc).