How to use localized RESX in Blazor WASM?

Rada Matěj 200

Hi,

all I want is standard "old way" usage of generated static properties of my RESX to localize texts based on CultureInfo and .culture.resx files. I've just figured out, that only difference from .NET Framework is that now in .NET 8 culture RESX naming is case-sensitive. With that, my .en-US.resx file is properly selected when culture is changed:

CultureInfo ci = CultureInfo.GetCultureInfo("en-US");
CultureInfo.CurrentCulture = ci;
CultureInfo.CurrentUICulture = ci;
string ddd = CommonStrings.ADTPFollowingDayTooltip;

However any other culture is falling into default RESX. Both cs-CZ and sk-SK cultures being absolutely ignored and even false RESX naming to any other culture is not going to switch from default RESX. However .en-US.resx file is correctly selected without anything changed in my basic WASM project - no Nugets or anything. I've also figured out how to load other cultures into WASM, however I still believe, that should not have any impact on RESX loading and seeking ... If I name any RESX by en-US culture, it is properly selected, but DE, FR, ... Nothing else is working (and falling back to default RESX).

(I have them properly included in project as embedded resources - just name change to en-US is working, so why not any other culture ...) Loading any other cultures is done by CSPROJ configuration (should not be needed):

<InvariantGlobalization>false</InvariantGlobalization>
<WasmIcuDataFileName>icudt_no_CJK.dat</WasmIcuDataFileName>
<BlazorWebAssemblyLoadAllGlobalizationData>true</BlazorWebAssemblyLoadAllGlobalizationData>

Tiny Wang-MSFT 2,006 Reputation points Microsoft Vendor

2024-05-23T01:46:31.7933333+00:00

Hi @Rada Matěj， I'm not able to reproduce your issue and investigate it based the code snippet and description. Could you please share more details about your issue like which document you followed to achieve your requirement, what are your codes, file structure, etc. Thank you!
Rada Matěj 200 Reputation points

2024-05-23T05:12:11.69+00:00

Well, I am using directly RESX, so I do not understand what document should I follow. I have bunch of .NET Framework 4.8 RESX files and I want to use them in Blazor WASM .NET 8. The only thing is, that I need 2 localizations. Meaning, that in sample Blazor WASM I've copied into:

Resources/Strings/CommonStrings/CommonStrings.resx

Resources/Strings/CommonStrings/CommonStrings.Designer.cs

Resources/Strings/CommonStrings/CommonStrings.en-US.resx

Resources/Strings/CommonStrings/CommonStrings.sk-SK.resx

And I am using them directly by Designer.cs static properties:

CommonStrings.MyString

Nothing more. With that basic WASM my default RESX is working and also switching into en-US is working. However sk-SK is not working and cs-CZ also not working. All I want is to use Designer.cs so that localization all over my application is checked at build-time, so that programmers cannot make mess. If there is more than just basic usage of RESX, that is my question here. I do not think so, because en-US switching is working, so probably I just need somehow to register other cultures, or what? de-DE or other languages also do not switch - however en-US is alway properly translating into English ...
Tiny Wang-MSFT 2,006 Reputation points Microsoft Vendor

2024-05-23T08:32:09.45+00:00
Hi Rada, thanks for your reply. First of all, we have official tutorial for globalization and localization. You might skim the documents to check whether you missed any configuration since you mentioned en-US switching is working but others not. For example, checking whether we had configuration like codes below.

builder.Services.Configure<RequestLocalizationOptions>(options => { var supportedCultures = new[] { "en-US", "fr" }; options.SetDefaultCulture(supportedCultures[0]) .AddSupportedCultures(supportedCultures) .AddSupportedUICultures(supportedCultures); });
Rada Matěj 200 Reputation points

2024-05-23T09:35:55.2866667+00:00

That seems odd to install into WASM, however no - this is not working either. Look - en-US RESX is working:

Any other culture is resulting into default RESX:

Which almost good enough for me - however we would still like third language also. I understand, that WASM as some limited localization at begin because of limited space in Browser. However I am missing what is needed to configure/install to support just one another RESX language ...

Rada Matěj 200

With:

using Grpc.Net.Client;
using Grpc.Net.Client.Web;
using ANeT.WebGuardWASM;
using ANeT.Contracts;
using Microsoft.AspNetCore.Components;
using Microsoft.AspNetCore.Components.Web;
using Microsoft.AspNetCore.Components.WebAssembly.Hosting;
using System.Text.RegularExpressions;
using ProtoBuf.Grpc.Client;
using Microsoft.AspNetCore.Builder;

var builder = WebAssemblyHostBuilder.CreateDefault(args);
builder.RootComponents.Add<App>("#app");
builder.RootComponents.Add<HeadOutlet>("head::after");

Uri baseAddress = new Uri(builder.HostEnvironment.BaseAddress);

builder.Services.AddScoped(sp => new HttpClient { BaseAddress = baseAddress });
builder.Services.AddAutoMapper(typeof(ANeT.SharedData.SharedMapperProfile));
builder.Services.Configure<RequestLocalizationOptions>(options => { string[] supportedCultures = ["en-US", "de-DE", "cs-CZ"]; options.SetDefaultCulture(supportedCultures[0]).AddSupportedCultures(supportedCultures).AddSupportedUICultures(supportedCultures); });

Still falling into default RESX (recognizing only en-US culture):

User's image

Tiny Wang-MSFT 2,006 Reputation points Microsoft Vendor

2024-05-24T02:42:02.3166667+00:00

Hi @Rada Matěj thanks a lot for your replying, it looked weird, could you please share with me a minimal sample which could reproducing the issue so that I could investigate it in my side?
Rada Matěj 200 Reputation points

2024-05-24T05:34:00.98+00:00

Hi,

I really do not understand how more minimal sample can be - I just create fresh WASM project, add single line RESX and only working culture is en-US ...

https://file.io/r1paJQGAHdCm
Tiny Wang-MSFT 2,006 Reputation points Microsoft Vendor

2024-05-24T05:47:00.4166667+00:00

Thank you very much @Rada Matěj but we are not able to download your attachment. Do you mean that you create a new WSAM project in .net 7? Then could you please share the complete Program.cs and the .razor file which containing the usage of the cultural localization? And one of the resx file content?

Rada Matěj 200

using Microsoft.AspNetCore.Components.Web;
using Microsoft.AspNetCore.Components.WebAssembly.Hosting;
using MinimalSample;

var builder = WebAssemblyHostBuilder.CreateDefault(args);
builder.RootComponents.Add<App>("#app");
builder.RootComponents.Add<HeadOutlet>("head::after");

builder.Services.AddScoped(sp => new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) });

await builder.Build().RunAsync();

using MinimalSample.Resources.Strings.CommonStrings;
using System.Globalization;

namespace MinimalSample.Pages
{
    public partial class Home
    {
        protected override Task OnInitializedAsync()
        {
            CultureInfo culture = CultureInfo.GetCultureInfo("en-US");
            CultureInfo.CurrentCulture = culture;
            CultureInfo.CurrentUICulture = culture;
            //CommonStrings.Culture = culture;
            var ddd = CommonStrings.ADTPFollowingDayTooltip;
            return base.OnInitializedAsync();
        }
    }
}

Tiny Wang-MSFT 2,006 Reputation points Microsoft Vendor

2024-05-24T09:15:22.84+00:00

Sorry Rada, I can't reproduce your issue based on your code snippet and screenshot you shared, I even can't pass the compilation.
Rada Matěj 200 Reputation points

2024-05-24T09:30:49.1933333+00:00
I've provided full Solution. How can you not pass in compilation of basic WASM created by Visual Studio (2022)? It is buildable of course - sample Blazor solution without any page or anything at all. Just Home page and single CSS. Nothing more. And then just 3 RESX - default, en-US and sk-SK. What can fail to compile here?

en-US:

<data name="ADTPFollowingDayTooltip" xml:space="preserve"> <value>Move to the next day</value> <comment>js</comment> </data>

cs-CZ (default RESX):

<data name="ADTPFollowingDayTooltip" xml:space="preserve"> <value>Posunout na následující den</value> <comment>js</comment> </data>

sk-SK:

<data name="ADTPFollowingDayTooltip" xml:space="preserve"> <value>Posunúť na nasledujúci deň</value> <comment>js</comment> </data>

Another link to sample SLN:

https://drive.google.com/file/d/1AD4N8UOBi3L-7UPMql57z_Z1rvZej7Jv/view?usp=sharing
Rada Matěj 200 Reputation points

2024-05-24T10:01:37.92+00:00
I've provided full Solution. How can you not pass in compilation of basic WASM created by Visual Studio (2022)? It is buildable of course - sample Blazor solution without any page or anything at all. Just Home page and single CSS. Nothing more. And then just 3 RESX - default, en-US and sk-SK. What can fail to compile here?

en-US:

<data name="ADTPFollowingDayTooltip" xml:space="preserve"> <value>Move to the next day</value> <comment>js</comment> </data>

cs-CZ (default RESX):

<data name="ADTPFollowingDayTooltip" xml:space="preserve"> <value>Posunout na následující den</value> <comment>js</comment> </data>

sk-SK:

<data name="ADTPFollowingDayTooltip" xml:space="preserve"> <value>Posunúť na nasledujúci deň</value> <comment>js</comment> </data>

Another link to sample SLN:

https://drive.google.com/file/d/1AD4N8UOBi3L-7UPMql57z_Z1rvZej7Jv/view?usp=sharing

Accepted answer

Tiny Wang-MSFT 2,006 Reputation points Microsoft Vendor

2024-05-27T09:35:12.7533333+00:00

Hi @Rada Matěj, I reproduced your issue finally in my side with your resource file and I also test if within blazor server app, and I found the issue only occurred in blazor wsam project, but in server app, it worked well.

This shall be the expected behavior of blazor wsam as CultureInfo.GetCultureInfo is defined as retrieving a cached, read-only instance of a culture, which only work in the server side.

When we want to get different results based on different culture in blazor wsam app, we need to follow this section. I had a test in my side which worked well. In the meantime, it requires to reload the application by using Navigation.NavigateTo(Navigation.Uri, forceLoad: true);

==============================================

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Best regards,
Tiny
Please sign in to rate this answer.

1 person found this answer helpful.
Rada Matěj 200 Reputation points

2024-05-27T10:25:15.6933333+00:00

Da! Obviously - yes, I understand now ... How would thread-static (culture) work on single-thread engine. Of course it needs reload. That was the whole problem. There is no need for anything else - just not to be stupid and changing ThreadStatic variable on single-thread environment. Thank you!
Sign in to comment

Share via

How to use localized RESX in Blazor WASM?

0 additional answers