ASP.NET MVC 2 Localization and Local Resource Files

The complete guide to localization with Global Resources is at While my keyboard gently weeps – ASP.NET MVC 2 Localization complete guide but here’s a simple summary:

Using Global Resources for Asp.NET MVC Localization Quick Start

  1. Create ordinary resource files in your project and fill ’em up.
  2. Add a Page Import directive to your MVC view:
    <%@ Import namespace=”My.Project.Name.PathTo.WhereverYourResourceFileIs” %>
  3. Behold the compiled fields available to you in intellisense:
    <%=ResourceFileName.MyPropertyName %>

Using Local Resources for Asp.NET MVC Localization Quick Start

The net and his dog seems to want to discourage you from using Local resource files with MVC. There are two or three riddles and here’s how to solve them:

  1. Right click your view directory. choose Add -> Add Asp.Net Folder -> App_LocalResources.
  2. Create resource files in there with names to exactly match the View name (so you end up with MyView.aspx.resx as the file name).
  3. Change the access modifier from its default No Code Generation to Public
  4. Type in your resource strings
  5. Add a Page Import directive to your MVC view:
    <%@ Import namespace="My.Project.Name.Views.ViewName.App_LocalResources" %>

    . Get the exact namespace by opening up the Resource File’s aspx.Designer.cs file.

  6. While you’re in the resource Designer.cs file note the class name: ActionName_aspx
  7. Behold the compiled fields available to you in intellisense:
    <%=ActionName_aspx.MyPageSpecificPropertyName %>
  8. Be awed and depressed when you build and run and get the error message ”Could not find any resources appropriate for the specified culture or the neutral culture. Make sure …. etc etc”. Fix this by clicking on the resx file in solution explorer and changing its Build Action from Content to Embedded Resource.. (thanks to http://www.devproconnections.com/article/aspnet22/ASP-NET-MVC-Localization for this point).

Leave a Reply

Your email address will not be published. Required fields are marked *