Provide .NET language packs on Web Apps
I'm working on a website that uses System.ComponentModel.DataAnnotations
On my local machine, model validation messages are displayed in french but they are in english when I deploy the website to Azure.
Please install .NET language packs on Azure Web Apps so we don't have to create .resx files and messy code to override .NET built-in messages...
Julien
shared this idea
Hi there,
We are still waiting on a few internal dependencies before we can complete this request.
Thanks,
Oded
18 comments
-
goisk
commented
Hello, can u say something about a https://mrecorder.com/ mobile recorder on Android. How can we use this application in our phones?
-
Anonymous
commented
> We are still waiting on a few internal dependencies before we can complete this request.
FYI you have been waiting for at least 18 months for "a few internal dependencies"
-
Артем Т.
commented
This is really necessary not only in Azure App Service, but in a Function app also.
-
Reiner Schramm
commented
Today, last statement from admin is 1 year ago ... "still waiting on a few internal dependencies" ... Is it still "under review" since 1 year and are you really still waiting? Would appreciate if you could give us a timeline.
Thanks,
Reiner -
Nahuel Prieto
commented
Any news yet?
-
Raj
commented
People !! Can this be arranged on a per WebApp basis through a Support Request ? And When is the earliest we can expect ?
-
Ivan R. Toledo Ivanovic
commented
Will this be fixed soon? Don't want my developers to waste hours fixing something that works fine on premises.
-
Anonymous
commented
Hey Guys, has this been resolved? am running into the same issues here?
-
Will Barry
commented
Is there a temporary solution so that language packs can be used on an Azure web app? Seems crazy to have to create translations for all the validation attributes when the translations have already been done. Is there a way to add via npm/nuget or use an assembly reference?
-
Carlos Gutierrez
commented
We need this to show end users the result of XML schema validations.
-
Nahuel Prieto
commented
Dear @Oded, how much more until we can see this working?
-
hai du huynh duy
commented
same problem with japanese system
-
Fraser
commented
Has there been any update on this? Also running into the same issue with the en-HK culture.
-
Waldemar Kubic
commented
we are waiting...
-
david
commented
It is absolutely necessary that you can choose the language pack as needed.
-
Sam Maurus commented
Unless I'm missing something, CultureInfo for en-HK is not available for .NET code running on Azure App Service ("CultureNotFoundException: Culture is not supported. en-HK is an invalid culture identifier"). On Azure Cloud Services, the latest guest OS includes this culture and many others.
I guess this is related to automatic OS update management, which Azure App Service should do automatically. I'm uncertain as to what factors are involved for making the latest .NET cultures available in App Service. Will these cultures be made available soon, or is there some reason why they're not supported?
Note that I'm talking about "out of the box" cultures, NOT custom cultures. For custom cultures I understand that one would be best to go for a Cloud Service approach where a task with elevated privileges would be required to register them.
-
Yanal
commented
+1 Please deploy the .net language packs on Azure Web app or allow user to choose what language pack should be deployed.
-
Julien
commented
There is a lot of people experiencing issues when they deploy their application to Azure : on their local machine, they have the right .NET language pack installed so they see model validation messages in their language. But when they deploy to Azure, model validation messages are in english (as Azure Web Apps don't have any language pack) and there is no other way to localize those messages than overriding DataAnnotations attributes or messing code by adding loads of Resource=typeof(dfgdfgdfg)