How to use resources in seperate project?

[stg609]

Tried different ways, but no luck. Hope there's a sample solution tell us how to make it.

---

Document Details

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

• ID: d1833676-ff1b-c587-cc9c-81afffa8ef68
• Version Independent ID: ad989395-3f49-4d55-521e-cf6fe56281ee
• Content: Globalization and localization in ASP.NET Core
• Content Source: aspnetcore/fundamentals/localization.md
• Product: aspnet-core
• Technology: aspnetcore-fundamentals
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[Rick-Anderson]

@stg609 tried what? What didn't work? What did you expect?

[stg609]

What did I expected?
We expect there's an official guideline to show us how to make use of the localized resource in a seperate project. Because we can't get it to work after google a lot.

What didn't work?
Following the doc, we can get the localized string as expected. But after we moved the whole resources folder to another project, than we can't get the localized string anymore.

What did we tried?
1、Ensure the project name is the same as the default assembly name
2、Create a AssemblyInfo.cs, and add [assembly: ResourceLocation("Resources")]
3、Remove the ResourcePath when calling services.AddLocalization

None of them works.

I have created a repo if anyone needed.

@Rick-Anderson

[hishamco]

@stg609 please check the troublshooting section before I dig into your code?

[Rick-Anderson]

This is not a localization issue. It's a getting resources from another project issue that should probably be opened with Visual Studio feedback.

[hishamco]

This may caused by ResourceLocation, RootNamespace or miss localization configuration

[LazZiya]

Tried different ways, but no luck. Hope there's a sample solution tell us how to make it.

I've created a sample repo with resources in external project, you may see it here.

The sample is based on the basic Asp.Net Core 2.2 template and it contains:

• Custom (route) RequestCultureProvider
• Custom IStringLocalizer
• Localization of :
  • Views
  • DataAnnotations
  • IdentityErrorDescriber error messages
  • Model binding and model validation error messages
  • Client side validation error messages
• Client side validation of localized input for different cultures (e.g. 12,34 and 12.34)
• All using shared resources

Notice: In the releases after v0.0.3 I moved the resources to the main project folder just to simplify the sample for beginners.

[hishamco]

@Rick-Anderson can we closed this while the issues has been answered and there's no respond from the author

[okofahi]

i still cannot resolve this issue.
The main project cannot display the localized strings from the Models class library.

[hishamco]

@okofahi do you a repo that reproduce the bug, but before that please check the troubleshooting guidance