Improve localization support in DataAnnotations
Today it's impossible to fully localize the view models / validations without using hacks or clutter the view models with the ErrorResourceName etc.
It would be a lot easier to handle localization if you created an extension point where one could register custom string providers.
We have opened a tracking bug for this issue to see if we can make this better.
The localization must be better, localization string resources must be able to get from custom provider like sql, xml, json, etc.
I really like the way "QT" uses for translations. we must be able to add, modify or remove string resources at runtime, or programatically.
The link to the GitHub page still does not work. Is it a private repository?
Peter Šulek commented
Linke "https://github.com/aspnet/DataAnnotations/issues/43" does not work for me.
Sergey Litvinov commented
Does the link to issue on DataAnnotations repo correct or maybe the repo itself is private? Because it shows 'Page not found' for me.