[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Report and Dashboard Server
[Collapse]eXpressApp Framework
 [Expand]Getting Started
  [Expand]Application Solution Components
   Client-Side Mobile Application
  [Expand]Business Model Design
  [Expand]Application Model
  [Expand]UI Construction
  [Expand]Extend Functionality
  [Expand]Data Manipulation and Business Logic
  [Expand]Security System
    Localization Basics
    Localize Standard XAF Modules and DevExpress Controls Used in an Application
    Localization Tool
    Culture-Specific Formatting
  [Expand]System Module
  [Expand]Extra Modules
  [Expand]Debugging, Testing and Error Handling
  [Expand]Application Life Cycle
 [Expand]Design-Time Features
 [Expand]Task-Based Help
  Frequently Asked Questions (FAQ)
 [Expand]API Reference
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
This documentation page describes implementations made in our v17.2 release cycle. To learn about functionality shipping with v18.1, navigate to our updated help file experience at docs.devexpress.com. Learn More


Localization is one of the primary features the eXpressApp Framework can offer, as a result of having the user interface model at the core of the configuration subsystem. Every WinForms, ASP.NET and Mobile XAF application is easily localizable using the Model Editor. A lot of localizable property values in the model are calculated based on other values, so you never need to change things like field captions in more than one place, unless they are actually supposed to be different.

To learn more about localizing the XAF applications, please refer to the following topics:

Expanded Concepts

Expanded Tutorial

Expanded Task-Based Help

Is this topic helpful?​​​​​​​