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 Global Resources (Obsolete from 11.2)

Starting with version 11.2, we recommend using a universal localization approach for all of our controls.
See the Localizing ASP.NET Controls via Satellite Resource Assemblies topic to learn more.
This topic describes the native ASP.NET approach. It is included in the documentation for compatibility purposes.

DevExpress ASP.NET controls can obtain content (e.g., captions, messages, etc.) based on the preferred language setting for the browser, or based on the user's explicit language of choice. Content is referred to as "resources", and it can be stored in resource files. A resource file is an XML file that contains strings that can be translated into different languages. Resource files in ASP.NET have a .resx extension. Each localized resource file contains key/value pairs. For detailed information, see ASP.NET Web Page Resources Overview.

Since a resource file is an XML file, you can easily customize string values using a text editor.

All DevExpress ASP.NET products that can be localized are shipped with resource files: a default resource file and numerous localized versions (one for each culture). The default resource files (also called "fallback") are listed below.

DevExpress ASP.NET Product Default Resource File
Image and Data Browsing
Docking and Popups
Site Navigation and Layout
File Management
Multi-Use Site Controls
DevExpress_Web_vX_Y.resx
ASPxEditors Suite DevExpress_Web_ASPxEditors_vX_Y.resx
ASPxGridView DevExpress_Web_ASPxGridView_vX_Y.resx
ASPxHtmlEditor DevExpress_Web_ASPxHtmlEditor_vX_Y.resx
ASPxSpellChecker DevExpress_Web_ASPxSpellChecker_vX_Y.resx
ASPxTreeList DevExpress_Web_ASPxTreeList_vX_Y.resx
ASPxPivotGrid DevExpress_Web_ASPxPivotGrid_vX_Y.resx
ASPxScheduler DevExpress_Web_ASPxScheduler_vX_Y.resx

A localized resource file name consists of the corresponding default name and a culture name (see the National Language Support (NLS) API Reference topic in MSDN). For example:

  • DevExpress_Web_v12_2.resx - The default resource file for DevExpress ASP.NET controls.
  • DevExpress_Web_v12_2.de.resx - A resource file for the German localization of DevExpress ASP.NET controls.

For a collection of default and translated resources, refer to the Localized resources for DevExpress ASP.NET controls article in our Knowledge Base. On the right side of this webpage, note the "Attachments" section with a list of available packs, different for specific versions of DevExpress components. Use these links to download a package with resources appropriate for your component version.

Expanded How to Add Global Resources to a Web Site

Before localizing your website, copy all the required localized resource files, along with their default versions, from the downloaded package to the App_GlobalResources folder. This folder can be created as shown below.

Note that if only localized resource files are contained in this folder (e.g. DevExpress_Web_v12_2.de.resx), without the corresponding default resource file (e.g. DevExpress_Web_v12_2.resx), App_GlobalResources-related exceptions will occur.

When all required resource files are copied to the App_GlobalResources folder, the localization can be specified via the UICulture property. To learn more, see the How to: Set a Culture for an ASP.NET Web Page topic.

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