MVC 5 Razor视图文本本地化最佳方案咨询：资源文件还是IViewLocalization？

Hey there! Let's break down the best options for localizing view text in MVC 5 with Razor—since you're working with the native framework, the two main players are resource files (.resx) and view-specific localization (IViewLocalization-based). Each has its own sweet spots, so I'll walk through both with concrete examples to help you pick what fits your project.

Core Idea #

Resx files are the most mature, widely used native solution. You can split them into global resources (shared across the entire project) and local resources (tied to specific views/controllers). They support strong typing, IDE intellisense, and compile-time error checking—great for keeping your localized text organized.

Step-by-Step Example #

(1) Create Global Resource Files

• Right-click your project → Add → ASP.NET Folder → App_GlobalResources.
• Inside this folder, create two files:
  • GlobalTexts.resx (default language, e.g., English; set its "Access Modifier" to Public in the properties window)
  • GlobalTexts.es.resx (Spanish version, matching the language code es)
• Add key-value pairs to each file:
  • English: WelcomeMessage → "Welcome to our platform!"
  • Spanish: WelcomeMessage → "¡Bienvenido a nuestra plataforma!"

(2) Reference in Razor Views

<!-- Direct reference to global resources -->
<h1>@Resources.GlobalTexts.WelcomeMessage</h1>

<!-- Use HtmlHelper's localization extension for cleaner markup -->
<p>@Html.Localize(Resources.GlobalTexts.AboutUs)</p>

(3) Strongly Typed Resources (Recommended)

Right-click your .resx file → Properties → Set "Custom Tool" to PublicResXFileCodeGenerator. This generates a strongly typed GlobalTexts class, so you can write:

<h1>@GlobalTexts.WelcomeMessage</h1>

This gives you intellisense and catches typos at compile time—way less error-prone!

Core Idea #

If you have text that's unique to a single view (and you don't want to clutter global resources), use view-bound local resources or IViewLocalizer. This keeps your localization files modular and tied directly to the views they serve.

Step-by-Step Example #

(1) Create View-Specific Resource Files

• For Views/Home/Index.cshtml, create a Resources subfolder inside Views/Home.
• Add two files:
  • Index.en.resx (English for the Index view)
  • Index.es.resx (Spanish for the Index view)
• Add view-specific keys:
  • English: PageSubtitle → "Your go-to hub for all things MVC"
  • Spanish: PageSubtitle → "Tu centro de referencia para todo lo relacionado con MVC"

(2) Call Local Resources in the View

<!-- Use HttpContext to fetch view-specific resources -->
<h2>@HttpContext.GetLocalResourceObject("~/Views/Home/Index.cshtml", "PageSubtitle")</h2>

<!-- Create a reusable helper (put this in App_Code/LocalizationHelpers.cshtml for global access) -->
@helper ViewLocalize(string key) {
    @HttpContext.GetLocalResourceObject(ViewContext.ViewPath, key)
}

<!-- Use the helper for cleaner code -->
<h2>@ViewLocalize("PageSubtitle")</h2>

(3) IViewLocalizer with Dependency Injection

If your project uses an DI container (like Unity or Autofac), inject IViewLocalizer into your controller and pass it to the view:

public class HomeController : Controller
{
    private readonly IViewLocalizer _localizer;

    public HomeController(IViewLocalizer localizer)
    {
        _localizer = localizer;
    }

    public ActionResult Index()
    {
        ViewBag.ViewLocalizer = _localizer;
        return View();
    }
}

Then in the view:

<h2>@ViewBag.ViewLocalizer["PageSubtitle"]</h2>

If you need more flexibility—like storing localized text in a database, dynamic language switching, or bulk resource management—libraries like NGettext or ResXManager can help. But for most standard MVC 5 projects, the native solutions above are more than sufficient.

• Go with resource files if you have shared text across multiple views/controllers, want strong typing, or prefer compile-time safety.
• Go with view-specific localization if you want modular, view-tied resources and want to avoid bloating your global resource files.

内容的提问来源于stack exchange，提问作者Mikkkel Bach