Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Localization resources error #26

Open
MaximTarasevich opened this issue Jul 27, 2022 · 7 comments
Open

Localization resources error #26

MaximTarasevich opened this issue Jul 27, 2022 · 7 comments

Comments

@MaximTarasevich
Copy link

I have localization implemented with Microsoft.Extensions.Localization package. And I am face with this error:
Снимок экрана 2022-07-27 в 17 35 59
What do you recommend to do with it?

@kevinbourassahoule
Copy link

@MaximTarasevich We're also facing this error, did you find a solution or did you abandon the package?

@stavroskasidis
Copy link
Owner

Are you using the latest version? There was a bug with resource files recompression that was fixed in the latest version.

@kevinbourassahoule
Copy link

We are, v2.4.0. We're not using the Microsoft.Extensions.Localization package on our end though, we're using simple .resx files. I don't know how to reproduce it unfortunately, it's not clear what the problematic environments have in common.

@kevinbourassahoule
Copy link

Some details: we have .resx files for the default English resources and .fr.resx files for the French resources, but it is only when we start the app with Blazor.start({ applicationCulture: "fr" }) that the app crashes with the above error. We tried with and without the BlazorWebAssemblyLoadAllGlobalizationData property from the MS docs.

I noticed from looking at the sample app's source that its resources are in a separate SampleAppsShared.Localization project. Is there any chance that having the resources in the Client project directly would cause this issue?

@stavroskasidis
Copy link
Owner

I will test that and come back to you.

@KalleKalve
Copy link

KalleKalve commented Jul 7, 2023

Any update on this?
Using the newest v2.4.5.
Same Error.

@KalleKalve
Copy link

Any update on this? Using the newest v2.4.5. Same Error.

To be fair, tested again after putting it aside, now it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants