Document home

Visual C++

ASP.NET Core Localization and Internationalization

ASP.NET Core (Wikipedia) is a popular cross-platform open-source web framework and the next-generation ASP.NET. ASP.NET Core contains three technologies: Razor Pages, MVC, and Web API. ASP.NET Core's online documentation contains useful topics. Read it first.

ASP.NET Core and Blazor use a new way to localize strings. They still use .resx file like every other .NET platforms, but you no longer need to create the original .resx files. All you have to do is to inject a localizer interface and then call localizer's this[string name] property for those strings that you want to localize.

The end of the document contains links to get the full source code of the samples.

Following instractions are for ASP.NET Core 3 and later.


Add Microsoft.Extensions.Localization NuGet package. Then add the following line to the _ViewImports.cshtml.

@using Microsoft.AspNetCore.Mvc.Localization
@inject IViewLocalizer Localizer

This will automatically inject IViewLocalizer into each view or page.

Internationalize view and page files

View and page files typically contain a lot of strings that need to be localized. For example, the following view contains a string in the title element.

<title>Driving Time Calculator</title>

To localize the title element, use the injected an IViewLocalizer.

<title>@Localizer["Driving Time Calculator"]</title>
If you did not add IViewLocalizer injection into _ViewImports.chtml you have to inject the localizer into each view or page.
@inject IViewLocalizer Localizer

Internationalize controller, view model and page model files

For controllers, view models, and page model, you perform similar steps. First, define a local IStringsLocalizer variable.

private IStringLocalizer localizer;

Then inject an IStringLocalizer<T> into the constructor and assign that into the local variable. Make sure you inject a generic version of IStringLocalizer and pass the type of the model into the localizer type.

public IndexModel(IStringLocalizer<IndexModel> localizer)
  this.localizer = localizer;

Finally, use the localize object in your code.

public void OnGet()
  Message = localizer["Enter values and click Calculate."];

Optionally you can also add a comment on the same line following the localizer call.

str = localizer["Enter values and click Calculate."];  //loc This is a comment

If you use String.Format or string interpolation such as

str = string.Format("Sport {0}", Value.Id);
str = $"Sport {Value.Id}";

use localizer

str = localizer["Sport {0}", Value.Id];  //loc 0: Id of the sport

Note! You cannot use the string interpolation with the localizer. For example, this won't work.

str = localizer[$"Sport {Value.Id}"];

This is because the interpolated string will be evaluated before passing to the localizer resulting a different string passed each time depending on the Id value.

This is all you have to do to get the strings ready for localization. Previously with ASP.NET, you had to manually create .resx files and add each string into these files. With ASP.NET Core, you no longer have to do this.

Modify Startup.cs

To enable IViewLocalizer we need to configure our project. Call AddViewLocalization in ConfigureServices.

public void ConfigureServices(IServiceCollection services)


If you MVC then use AddMvc() instead of AddRazorPages().

To use the localized resource files, we need to configure our project for localization. First, we need to specify the location where the localized .resx file is.

public void ConfigureServices(IServiceCollection services)

  services.AddLocalization(opts => { opts.ResourcesPath = "Resources"; });

Then we need to tell what are our supported locales and what the default locale. The following code adds English, German, and Finnish as supported cultures.

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
  if (env.IsDevelopment())

  // Begin I18N configuration
  var supportedCultures = new List<CultureInfo>
    new CultureInfo("en"),
    new CultureInfo("de"),
    new CultureInfo("fi")

  var options = new RequestLocalizationOptions
    DefaultRequestCulture = new RequestCulture("en"),
    SupportedCultures = supportedCultures,
    SupportedUICultures = supportedCultures

  // End I18N configuration




  app.UseEndpoints(endpoints =>

The above is the standard way to configure the middleware. However, it hard-codes the supported languages into your code. If you later add new languages, you need to modify the source code, compile, and deploy your application. To avoid this, we have implemented a class extension for IApplicationBuilder. The localization configuration takes only one line.

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
  // Begin I18N configuration
  app.UseRequestLocalizationWithAvailableLanguages(​Assembly.GetExecutingAssembly().Location, "en");
  // End I18N configuration

The above code configures the localization but also detects the deployed satellite assembly files and uses those languages when configuring the localization. To add a new language, you only have to deploy the satellite assembly file on the server. You can get the code from Soluling's NuGet package.

Data annotations

Most models contain data annotations such as property's display names and validation errors. APS.NET Core has built-in support for data localization annotation. Except for the annotations, you don't have to add anything else to the model. However, you have to configure the middleware to use the data annotation localization. Call AddDataAnnotationsLocalization in ConfigureServices.

public void ConfigureServices(IServiceCollection services)

You should add Display attribute to every property and enum values.

public enum SportKind
  [Display(Name = "Individual")]
  [Display(Name = "Team")]

Language select

ASP.NET Core uses culture providers to choose the current language. Each provider can set the language using its way. The purpose of a provider is to set Culture and UICulture of the thread handling the HTTP request. There are three built-in providers. They are:

Query string

QueryStringRequestCultureProvider provider uses a query string to pass the culture. Use culture parameter sets Culture and ui-culture parameter set UICulture. The following example sets the culture to Finnish in Finland.

If you only pass one parameter both Culture and UICulture are set the same value.


CookieRequestCultureProvider provider reads the Culture and UICulture parameters from a cookie. The default cookie name is .AspNetCore.Culture.


where c is Culture and uic is UICulture.


AcceptLanguageHeaderRequestCultureProvider provider reads the culture from Accept-Language HTTP header.

Default configuration

By default, ASP.NET Core localization configures the three above providers such a way that first query string is used (if any), then a cookie is used (if any), and finally, Accept-Language is used. If you don't pass the query parameter and you don't have a cookie, then the default language of the browser (i.e., Accept-Language) is used. You can override the Accept-Language by settings a cookie, and you can override the cookie by passing a culture parameter. For most users, this is what you want. However, if you want to store the active culture into a database, you can write your provider and configure it in Startup.cs.

What are the benefits of using Soluling when localizing ASP.NET Core and Blazor applications?

Soluling does not replace the built-in internationalization and localization method of ASP.NET Core and Blazor. Instead, Soluling extends it making application internationalization and localization much easier. The following list shows the Soluling features that help you when localizing ASP.NET Core and Blazor applications.

1) No need to manually create the original .resx files

ASP.NET Core and Blazor do not require the original .resx files to run the application in the original language. Still, they need localized .resx files to run the application in any other language. To create the localized .resx files, you will need the original .resx files as a template. So in practice, the original .resx files are required. It is a time-consuming and error-prone job to create them and make sure they are up to date. Here is where Soluling provides a huge help. Soluling reads your .csproj file to locate all your source code files (.cshtml, .cs, and .razor), finding the instances where a localizer interface or data annotation attributes has been used. When found, Soluling extracts the string passed to the localizer interface and writes the string into the right .resx file.

You no longer have to create and maintain the original .resx files, but Soluling creates them for you and always keeps them up to date. If you modify the string in the source code, you just run Soluling to update the resource files. In addition to extracting the strings and writing the original .resx files, Soluling also reads the string comments from your source code. Everything, your strings, and comments, are all in place in your source code, and you never have to write any .resx.

2) Specify only your Visual Studio project file

You only have to tell Soluling where you .csproj or .sln file is located. No need to select individual resource or source code files. If you later add new pages or components to your application, you don't have to change your localization settings at all.

3) Soluling creates the localized .resx files

After Soluling has created the original .resx files, it scans the .resx files extracting the strings. Use Soluling to translate the project. Finally, when building, Soluling creates localized .resx files. It also creates localized satellite assembly files.

All this can be done in your build process using Soluling's command-line tool, SoluMake.

Create Soluling project

Now when our application has been internationalized we can create a Soluling project for it. Start Soluling Drag your .csproj file into Soluling or click New from File or Files and browse the .csproj file. The project wizard appears, showing the Localizer options page.

ASP.NET Core options in Project Wizard

When using Soluling, you do not have to create the orginal resource files, but Soluling automatically scans your source code to create them. By default, the original resource file will only exist in the memory, but you can optionally also make Soluling write the files. Use the third option if you do the extraction by yourself. For most projects, the default settings work file. To learn the meaning of each option, read the documentation.

Click Next. The Resources page appears. Accept the default settings where only the .resx files are localized.

ASP.NET Core options in Project Wizard

Click Next. If there are existing localized files, Solulng shows the Import existing localizer files page. You can selecet the languages that are imported.

ASP.NET Core options in Project Wizard

Click Next. Select Languages page appears. Add the languages you want to support and also select the original language.

Select languages

We added Finnish and German as target languages and English as the original language. Complete the wizard by clicking Finish. A new project appears.

Enter the translations or let you translator to translate the project. Learn more about how to translate a project. Once translated, you can create localized resource files.

Localized views

If you use MVC, there is another option to localize view files (.cshtml). Instead of using Localizer in your views and using .resx to localize them, Soluling can make localized versions of the view files. To enable view file localization, check HTML resources in the Resources sheet.

Localize view files

The benefit of the view localization is that you do not have to modify your view by injecting and adding localizer. Instead, you can use hard code strings in HTML markup or script parts. To learn more about view file localization see <data-dir>\Samples\ASP.NET\Core\MVC/DrivingView sample.

Note! Razor Pages do not currently support localized page files, so using the localizer is the only option. Web API does not even use view/page files, so there is no need to localize them.


GitHub and <data-dir>\Samples\ASP.NET\Core contains sample sub directories for each ASP.NET Core programming models.


GitHub and <data-dir>\Samples\ASP.NET\Core\MVC contains following ASP.NET Core MVC samples:

GitHub/Directory Description
Driving A simple driving time calculator sample that shows how to localize strings and images and how to use plural enabled message strings.
DrivingView As above but each view file has a set of localized view files.
HelloWorld A localized Hello World application.
Minimal A minimal localized application.

Razor Pages

GitHub and <data-dir>\Samples\ASP.NET\Core\RazorPages contains following ASP.NET Core Razor Pages samples:

GitHub/Directory Description
Driving A simple driving time calculator sample that shows how to localize strings and images and how to use plural enabled message strings.
Sport A simple localized sport application that use the multilingual sport API (see below). Learn more about the application from here.


GitHub and <data-dir>\Samples\ASP.NET\Core\WebAPI contains following ASP.NET Core Web API samples:

GitHub/Directory Description
SimpleAPI A simple multilingual API that uses hard coded resources. Implements only GET method.
SportAPI A multilingual API that stores sport in a database. Implements a CRUD (Wikipedia) API. Learn more about the application here.