MVC seems all the rage these days. And while there are many good things it brings to the table, it seams it takes us a step back in terms of I18N.
For instance, if you want to use the special aspx attribute meta:resourceKey=”foo”, you won’t always be able to do so.
The following would work fine:
But we’re out of luck with buttons:
At runtime, you will get an exception explaining you need a FORM with a runat=”Server”. Ugh. After some spelunking I came across this discussion, which basically suggests creating an extension to the System.Web.Mvc.HtmlHelper class. The discussion is thick with issues, specifically that if a UserControl is used, finding it’s path in order to get to it’s local resource requires all manners of digging around compilation and application with fairly extensive branching and parsing. Ultimately, the extension is complicated by attempting to combine both a resource retrieval, fallback to global from local resource and formatted template substitution in one. A good helper – if the kinks are worked out.
So I wrote my own syntactic sugar to do the same:
It is substantially shorter and defers to a base class.
System.Web.MVC.ViewUserControl inherits from
System.Web.UI.UserControl, so the call is true to it’s application. I also extend
Lastly, there is the issue of a global resource. Since these resources are compiled and accessed at design time using dot notation (MyGlobalRes.MyKey) I felt that providing an extra function would not significantly shorten code or simplify developer’s life. That is, given a resx file in the App_GlobalResources containing the file Zones.resx, containing a key Zone1 one would simply write out
or – if your resource is a template requiring tokens to be merged:
Happy MVC Internationalization, localization and globalization!