What is the best way to make an ASP.NET MVC multi language website?

The following code is what I use, but I need to make sure from your real-world experience that my code is the best way for performance to set language in the Application_AcquireRequestState method because I noticed that the method get is called twice in every request.


public static void RegisterRoutes(RouteCollection routes)

        name: "Default",
        url: "{language}/{controller}/{action}/{id}",
        defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional, language = "en-US" }



protected void Application_AcquireRequestState(Object sender, EventArgs e)

    if (HttpContext.Current.Request.RequestContext.RouteData.Values.ContainsKey("language"))
        var language = (string)HttpContext.Current.Request.RequestContext.RouteData.Values["language"];
        if (language != null)
            Thread.CurrentThread.CurrentCulture = new CultureInfo(language);
            Thread.CurrentThread.CurrentUICulture = new CultureInfo(language);

Here are the action links that I use to pass the language parameter:

 @Html.ActionLink("English", ViewContext.RouteData.Values["action"].ToString(), ViewContext.RouteData.Values["controller"].ToString(), new { language = "en-US" }, null)
 @Html.ActionLink("French", ViewContext.RouteData.Values["action"].ToString(), ViewContext.RouteData.Values["controller"].ToString(),new { language = "fr-FR" },null)
  • \$\begingroup\$ I would recommend using resource files. You can handle user specified languages, as well as the browser languages, without having to use multiple views for each. \$\endgroup\$
    – Bardicer
    Mar 2 '18 at 16:19

I see the solution you proposed is very good, one small thing I want to recommend here, which is to validate the language value is a valid culture before using it in the Global.asax to avoid the application exception if someone manually modified the value on the URL to invalid culture value. In addition, you can simplify the URL to only use EN/FR instead of full culture code "en-US".

In our application, because we support Arabic language which requires to render the application from Right to Left, we found it is better to load totally different views for each culture, not just the resource files. So we changed the views folder to have EN & AR folders, each folder has its localized views, then customized the MVC view engine to dynamically load the right view based on the routing data.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.