You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 29, 2018. It is now read-only.
I have an ASP.NET Core Web App (version 1.1) using Resources files for Localization/Globalization.
On localhost all resources are found, but on Azure the localizer only founds resources for Views.
For example, the resource file Controllers.HomeController.en-US.resx works ok in localhost but on Azure it only works if I rename it to Namespace.Controllers.HomeController.en-US.resx. On localhost the second name does not work.
The text was updated successfully, but these errors were encountered:
@sanchapereira I am not having this issue with .Net Core 1.1 uploaded to Azure from VS 2017 RC. My resource file is Controllers.HomeController.en-US.resx and the same file with fr-FR
@sanchapereira it's hard to know without seeing your code, but I suspect you have the same (or a similar) problem as #314, namely that your namespace isn't matching the assembly name of your project. Please review #314 and the "Resource file naming" section of this documentation. If you're still having trouble after that then please upload a minimal reproduction app and link it here so I can take a look.
Uh oh!
There was an error while loading. Please reload this page.
I have an ASP.NET Core Web App (version 1.1) using Resources files for Localization/Globalization.
On localhost all resources are found, but on Azure the localizer only founds resources for Views.
For example, the resource file Controllers.HomeController.en-US.resx works ok in localhost but on Azure it only works if I rename it to Namespace.Controllers.HomeController.en-US.resx. On localhost the second name does not work.
The text was updated successfully, but these errors were encountered: