Skip to main content
BuyLog In
ASP.NET MVC Extensions
Search in…
Docs > Common Concepts > Localization
All docs
V24.1
ASP.NET MVC Extensions
Prerequisites
Supported Browsers
What's Installed
Get Started
Upgrade to a New Version
Common Concepts
Web.Config Modifications
Data Binding
Callback-Based Functionality
Client-Side Functionality
Using Extensions in Razor Views
Declaring Server-Side Event Handlers
Templates
Appearance Customization - Theming
Data Annotation Attributes
Accessibility Support
Right to Left Support
Mobile Support
Cookies Support
Localization
Satellite Resource Assemblies
Localizer Objects
Global Resources
Performance Optimization
Office Document Management
Cloud Storage Account Management
Web Farm and Web Garden Support
Components
Security Considerations
Redistribution and Deployment
Troubleshooting
Get More Help
.NET Framework API Reference
Client API Reference
Download CHM

Localization

DevExpress .NET products can be localized for specific languages and locales. You can localize UI element text (such as dialog boxes, button captions, menu items and error messages), numbers, date and time values, and currencies.

LocalizationResult

You can use the following approaches to localize DevExpress ASP.NET MVC extensions.

  • Satellite Resource Assemblies

    The most common approach for the .NET Framework. DevExpress provides a Localization Service that allows you to modify existing translations, and compile and download satellite assemblies.

  • Localizer Objects

    Use localizer objects to access resource string values and override them at runtime.

  • Global Resources

    The native ASP.NET approach. In v12.1 and higher, we recommend that you use the Satellite Resource Assemblies instead.

  • UI Localization Client

    The UI Localization Client allows you to quickly identify non-translated strings of DevExpress UI controls and translate them during a debug session. The utility automatically generates a RESX file(s) with translated resources and adds it to the project.

See Also