CODEWITHSUNDEEP
asp.net-mvc-3globalization
Vivek
Vivek

Reputation: 271

Globalization in ASP.Net MVC 3

I am trying to achieve globalization/localization in my MVC 3 application. I don't want different Views for each language. Please suggest how I can proceed. Any supported links/URLs will be of great help.

Upvotes: 27

Views: 16040

Answers (4)

Uwe Keim
Uwe Keim

Reputation: 40726

To add some details to Martin Booth's great answer (in case his MediaFire link might disappear), here is how I idid it:

I've used two files, since I only need English and German ("de") for now:

enter image description here

For the properties of each file, I had to manually enter the Custom Tool as well as the Custom Tool Namespace values, for each file:

enter image description here

enter image description here

And finally, I entered the following inside the root Web.Config file, below the <system.web> section:

<globalization uiCulture="auto" culture="auto" />

Of course I've also added the namespace directive in the Web.Config file below the Views folder (i.e. not the root one), as Martin describes:

<add namespace="ViewResources" />

And then I could finally access the resources strongly-typed in my (partial) Razor view:

<h2>@ViewResources.Test1</h2>

BTW: this worked with MVC 4, too, not only MVC 3.

Upvotes: 5

Riccardo Bassilichi
Riccardo Bassilichi

Reputation: 969

The next step that you need is to localize your Javascript library. Take a look here: MVC-JavaScript-localization-of-external-js-files

Upvotes: 1

user342552
user342552

Reputation:

Here is a great detailed post about MVC 3 Globalization/Internationalization http://afana.me/post/aspnet-mvc-internationalization-part-2.aspx

Upvotes: 5

Martin Booth
Martin Booth

Reputation: 8595

You localize it in the same way as any other application like this:

  1. Create a folder, call it e.g. Resources
  2. Right click the folder and add class... choose resource file. Call it anything you like e.g. Strings.resx
  3. Under the properties of file, change Custom Tool to be PublicResXFileCodeGenerator
  4. Populate the Resource file with Translation key and value pairs (this will be the default translation)
  5. Create other resources with the name of the culture they're for in this format: {name}.de.resx e.g. Strings.de.resx
  6. (This is for Razor) crack open the web.config in the Views folder and add this to /configuration/system.web.webPages.razor/pages/namespaces: <add namespace="Resources" /> (assuming resources is the name of the folder you created the resources in and you haven't changed the default namespace on the resouce files themselves). This step means you don't have to fully qualify the resource classes in your views each time you want to reference a translation.

  7. Use the translations in place of text in your views like with the following code:

    @Strings.MyString

Strings will be automatically translated in the view depending on CultureInfo.CurrentCulture but this is not set automatically for you

You will need to change the CurrentCulture (potentially in Application_BeginRequest). How you do this is up to you, it could be a route value which sets it or you can read the user's browser language

You can find a list of the user's prefered languages (in order) in HttpContext.Current.Request.UserLanguages.

Upvotes: 43

Related Questions