IStringLocalizer support in Blazor

[TPIvan]

Does the statement that "IStringLocalizer<> is supported in Blazor apps" mean that I may to inject and use it in my own code or is it used also internally (e.g. for localizing error messages)?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 15e7c51d-1839-1849-813a-23c4d21c64ae
• Version Independent ID: d6f07538-228e-9f96-680f-6c324caf11d6
• Content: ASP.NET Core Blazor globalization and localization
• Content Source: aspnetcore/blazor/globalization-localization.md
• Product: aspnet-core
• Technology: aspnetcore-blazor
• GitHub Login: @guardrex
• Microsoft Alias: riande

[guardrex]

Hello @TPIvan ... Yes, that's right. Here's how the JsonStringLocalizer example (one of the example projects listed at https://docs.microsoft.com/aspnet/core/fundamentals/localization-extensibility#localization-resources) demos it (injected into Configure) ...

https://github.com/hishamco/My.Extensions.Localization.Json/blob/master/samples/LocalizationSample/Startup.cs#L20

[TPIvan]

So it is not used by Blazor framework internally.

[guardrex]

Sorry ... I missed the 2nd part of your question. It seems yes ... it is used internally. However, the setup might not be as devs expect. I noticed various discussions on the subject that lead to me to believe that either cross-links or an outright example would be helpful. For example ...

• https://stackoverflow.com/questions/59659489/how-to-localize-validation-message-dataannotationsvalidator-in-blazor-server-s
• https://stackoverflow.com/questions/59033230/how-to-add-viewmodel-localization-to-blazor

I'd like to take a closer look at this. However, we're crazy busy these days, so I'll need to backlog this for a while until I get some free time to take a closer look.

If you need help, devs apparently have been working with localization in Blazor, including localization of error messages. Reach out on the usual support channels if you don't find what you need in blog resources and the ASP.NET Core docs in the main doc set ...

• Stack Overflow
• ASP.NET Core Slack
• ASP.NET Gitter

... and if you find out that it is simply using an ordinary approach already covered in the localization docs here ... in the MS doc set ... please do comment back here with that information. I would like to cross-link to our own content if possible.

[guardrex]

Note to self: dotnet/aspnetcore#12158.

[guardrex]

Ok ... I took a closer look. Loc issues are being addressed by engineering. They don't have a "loc" label, but searching blazor-labeled issues with "localization" turned up ...

https://github.com/dotnet/aspnetcore/issues?q=is%3Aopen+is%3Aissue+label%3Aarea-blazor+localization

I think what we call out in the topic as "supported" is correct today. Other loc features should be covered in the engineering issues or requested on the engineering repo. When data annotations are available, then we'll open an issue to cover it when the time comes.

I don't think we'll have time to add a dedicated loc sample. I'm having this little break for a few months to get caught up on issues, then 😅 5.0 preview issues are going to start appearing here.