Skip to main content
BuyLog In
WinForms Controls
Search in…
Docs > Build an Application > Localization
All docs
V23.2
WinForms Controls
.NET/.NET Core Support
Prerequisites
What's Installed
Build an Application
Choose Application UI
Skins
Localization
Localizing WinForms Controls via Satellite Resource Assemblies
Localizing WinForms Controls via Localizer Objects
Right-to-Left Layout
Printing and Exporting
WinForms MVVM
Accessibility Support
Automated UI Tests (UI Automation, Appium, Coded UI)
Redistribution and Deployment
How to: Perform Actions On Application Startup
Controls and Libraries
Common Features
Security Considerations
UI Templates
Desktop & Web App UI Framework (Powered by EF Core)
Get More Help
API Reference
Download CHM

Localization

  • 2 minutes to read

Localization allows you to translate DevExpress WinForms UI controls into different languages. From straightforward localization with pre-built satellite resource assemblies to manual translation of the UI using a comprehensive API, DevExpress WinForms UI controls include everything you need to quickly develop multicultural enterprise applications.

Localized UI Controls, DevExpress

Satellite Resource Assemblies

All DevExpress WinForms controls can be localized using satellite resource assemblies. DevExpress delivers satellite assemblies for a large variety of languages and cultures. Our DevExpress Unified Component Installer includes resource files for the following cultures: German (DE), Japanese (JA), and Spanish (ES).

Read the following topic for information: Satellite Resource Assemblies.

Important

How to avoid issues when localizing DevExpress WinForms UI controls using satellite resource assemblies

This technique allows you to easily translate or rename our shipping resources on the fly (for example, titles, menu commands, messages, etc.). Read the following topic for information and examples: Localizer Objects.

Note

The localization-related API takes priority over satellite resource assemblies.

Tip

Use our Online Localization Service to modify our shipping resources or create satellite assemblies for a different language.

Identification of Non-Translated Resources

  • Use our UI Localization Client tool shipped as part of your DevExpress subscription. This tool streamlines the entire localization process. You can quickly find non-translated strings and translate them during a debug session.
  • Handle the XtraLocalizer.QueryLocalizedStringNonTranslated event to collect non-localized resource strings for further translation. The event allows you to focus on strings that require translation in your application.

Include Satellite Assemblies in a Deployment

See Also