ASP.NET - MVC 3: Localization

Question

I am about to implement localization for my MVC3 web application. Googling my way through large amounts of ways to do it, I was left unsure which way to implement this. I fo

Answer 1

Then I found a post that warned about using the App_GlobalResouces and App_LocalResources. (Link)

I found that post extremely useful. The method explained there is very clean. Here is a snippet of my newly created index view using that method:

@using Resources.Index
@{
    ViewBag.Title = "Index";
}

<h1>@Index.Title</h1>

I don't think there is a definitive do-it-this-way-or-else method, so going for the cleanest method seems to me like a good deal.

Answer 2

I've come up with an easier way to handle localization where you don't have to use resource files or attributes. It involves custom metadata providers.

MVC3 uses metadata providers to get all text strings. My approach allows you to either use string tables, a database, flat files or any other source to provide the translations. All you need to do is to inherit two interfaces.

Read about it here: http://blog.gauffin.org/2011/09/easy-model-and-validation-localization-in-asp-net-mvc3/

Edit

Everything is now documented at github and there are nuget packages: https://github.com/jgauffin/griffin.mvccontrib