Globalization and Localization of Model Validation Message in MVC

In this quick post you will learn how to globalize and localize the model validation message in MVC Applications. At the end of this post, you will also learn how to display the localized message (greeting) on the page.
Here's the screen of what we are going to build.



I will use ASP.NET resource files to define the globalized (default) and localized strings and this string message will be displayed to user based on the request header language that client browser sends.

 I have recorded a video on this title, you can watch it.

Now, follow the steps from here:

Step 1

In order to do all by ASP.NET automatically we need to set the globalization settings in web.config, as given below.

<system.web>
  ....
  <globalization culture="auto" uiCulture="auto"/>
  ....
</system.web>

Step 2

To localize the text we have to rely on the resource files which nothing but a XML file with .resx extension that contains globalized and localized string messages, name and its value pair.

These resource files can be added anywhere in the application but I will prefer to add it with views.


Error.resx File

In this file I have defined two string names AddressRequired and NameRequired. This file can be called as default/base resource and will be display every time when browser requests language that we don’t support. Remember to change the access modifier to Public, because this file turns into assembly at compile time that required public access so that views can access it.

Error.hi.resx File

This file will have the localized name and value pair, which is Hindi language here. This string message will be displayed to user based on the request header language that client browser sends.

Step 3

In order to display these localized validation messages, we need make quick change in model validation attribute, here we go.

public class DemoFoolProofModel
{
    public int Id { get; set; }

    //[Required]
    [Required(ErrorMessageResourceType=(typeof(MvcApplication1.Views.Demo.Error)), ErrorMessageResourceName="NameRequired")]
    public string Name { get; set; }

    //[Required]
    [Required(ErrorMessageResourceType=(typeof(MvcApplication1.Views.Demo.Error)), ErrorMessageResourceName="AddressRequired")]
    public string Address { get; set; }
}

I am overriding the validation message displayed by [Required]. ErrorMessageResourceType will have the name of resource file and ErrorMessageResourceName will have name of name-value pair. That’s it.

Step 4

Now we are all set to run the application, hit F5, at the same time open fiddler to inspect the request header. I selected English (United States) as a primary language and you can see fiddler has ‘en-US’ in request header. In this case Error.resx file information will be rendered.


And here is the output in the browser.


Step 5

Let’s selected Hindi as a primary language and you can see fiddler has ‘hi’ in request header. In this case Error.hi.resx file information will be rendered.


Step 6

In the same way if you want to display some greeting on your website you can do this by adding another two resource files, as given below.


Now, to display this localized message on view page use following code:

<h2>@MvcApplication1.Views.Demo.Greeting.GreetingMsg</h2>

Now, select Hindi as a primary language, you will see it working.


Hope this helps.

Comments

Post a Comment

Popular posts from this blog

Migrating database from ASP.NET Identity to ASP.NET Core Identity

Image
As you know ASP.NET Core Identity (table structure) is different from what we had earlier in ASP.NET Identity. Actually the identity system which we have today with .NET Core is very mature and continuously evolved be it ASP.NET Membership, ASP.NET Identity 1, ASP.NET Identity 2 and now ASP.NET Core Identity. Recently I had to migrate few application to ASP.NET Core and similar its identity database. Because the table schema is changed, i had to re-think and create migration script which I would like to share with you today. It is very simple and easy, just three step and I had everything ready: STEP 1 : Change name of existing tables STEP 2 : Create ASP.NET Core Identity tables STEP 3 : Migrate data from old tables (ASP.NET Identity) to new tables (ASP.NET Core Identity) Script:  https://gist.github.com/itorian/c699e8534b392a6c726ec66c48100072 You should also watch my video, where I demoed migration.
Read More »

Customize User's Profile in ASP.NET Identity System

Image
Note: You should read this post instead, I found below walkthrough will not work on ASP.NET Identity 2. I will re-work on this post soon. In this post you will learn how to customize User’s Profile and add some more fields like FirstName, LastName, EmailID etc with ASP.NET Identity System. In my last post I listed some of the great new features introduced with Identity system .
Read More »

Lambda two tables and three tables inner join code samples

In this blog post you will learn inner join using lambda queries. There will be two samples, in first sample you will see how you can join two tables and in second sample you will see how you can extend even further to join three tables and so on. I will sample in-memory data, but the same implementation will work with IQueryable (lazy query) too. Here's the code snippet:- namespace ConsoleApp1 {     class Program     {         static void Main()         {             var table1 = new List<Table1>();             table1.Add( new Table1 { Id = 1, Name = "Name 1" , Address = "Address 1" });             table1.Add( new Table1 { Id = 2, Name = "Name 2" , Address = "Address 2" });             table1.Add( new Table1 { Id = 3, Name = "Name 3" , Address = "Address 3" });             table1.Add( new Table1 { Id = 4, Name = "Name 4" , Address = "Address 4" });   
Read More »