Log In
Home
Support
Demos
Documentation
Blogs
Training
Webinars
[Expand]General Information
[Expand]WinForms Controls
[Collapse]ASP.NET Controls and MVC Extensions
 [Expand]Prerequisites
 [Expand]What's Installed
 [Expand]Common Concepts
 [Expand]ASP.NET WebForms Controls
 [Expand]ASP.NET MVC Extensions
 [Collapse]Localization
   Localizing ASP.NET Controls via Satellite Resource Assemblies
   Localizing ASP.NET Controls via Localizer Objects
   How to: Set a Culture for an ASP.NET Web Page
   Localizing ASP.NET Controls via Global Resources (Obsolete from 11.2)
 [Expand]Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Document Server
[Expand]Reporting
[Expand]Report Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Expand]CodeRush
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Localizing ASP.NET Controls via Satellite Resource Assemblies

This document demonstrates the most common approach to localizing a .NET application using Satellite Resource Assemblies (libraries that contain translated resources). This is the standard localization mechanism provided by the .NET Framework, appropriate for world-ready multi-language applications. To learn more about localization, refer to the Localizing Applications topic in MSDN.

Note

Important: You can also localize your applications using custom localizers, but some controls contain form resources (e.g., the XtraReports Search dialog), and the only way to translate them is to create satellite assemblies. Thus, localization via resources is the preferable solution.

This document consists of the following sections.

Expanded Obtaining Satellite Assemblies

In most cases, you do not need to manually translate all language-specific resources, because DevExpress already delivers satellite assemblies for a large variety of languages and cultures.

Resource assemblies for some popular languages are provided by the .NET Products Installer. It registers these assemblies into the GAC (Global Assembly Cache) of your development machine, and also places them in the installation folder ("C:\Program Files (x86)\DevExpress 17.1\Components\Bin\Framework\", by default).

This folder contains a subfolder with translated libraries. Each subfolder is named according to common culture abbreviations:

  • de - German;
  • es - Spanish;
  • ja - Japanese;
  • ru - Russian.
Note

For a full list of available culture names, refer to the National Language Support (NLS) API Reference topic in MSDN.

If these folders do not contain assemblies for the language you require, or you wish to provide custom translations for specific UI elements, you can use the DevExpress Localization Service. This service allows you to download and modify the satellite assemblies required to localize applications created with DevExpress .NET controls.

For more information on preparing and downloading resource assemblies, refer to the Localization Service documentation, or watch the training video on YouTube.

Note

You can find the Resource String enumerations for DevExpress ASP.NET controls in the Localizing ASP.NET Controls via Localizer Objects topic and use them to search for the required localizable string within the translation table.

Expanded Adding Satellite Assemblies to Your Application

To add localized resources to your application, copy satellite assemblies from the unpacked archive to the corresponding subfolders of your application's directory. The subfolder's name is the culture's abbreviation. For example, to include German assemblies, copy the folder named de from the \Bin\Framework\ directory to the Bin directory of your application.

The following diagram illustrates where satellite assemblies should be placed within your application's directory.

Note

Alternatively, you can install satellite resource assemblies into the GAC. In this case, you can use these localizations in applications without copying satellite assemblies. In any case, deploying the assemblies to the production server is required.

Assemblies that are installed in the GAC are accessible in the Wizard Localization Tab.

When the required satellite resource assemblies are placed in the appropriate locations, the localization can be specified via the Culture and UICulture properties. To learn more, see the How to: Set a Culture for an ASP.NET Web Page topic.

How would you rate this topic?​​​​​​​