How to localize (translate) your DevExpress .NET products?
The best approach is to translate component resources and build satellite assemblies.
The DevExpress Localization Service is an efficient and user friendly way of downloading and modifying existing translations and source files for them online.
The Localization Service - Overview article describes how to use this new service.
In brief, this service allows you to alter the default translation online and request your own copy of satellite assemblies, which will be built for you and signed with the same strong key token we use for our main assemblies.
Once you receive an email with satellites assemblies, refer to the one following articles in help that illustrate how to localize our controls by using satellites assemblies:
How to: Localize DevExpress WinForms Controls Using Satellite Assemblies
How to: Localize DevExpress Asp.Net Controls Using Satellite AssembliesHow to: Localize DevExpress WPF Controls Using Satellite AssembliesHow to: Localize DevExpress Silverlight Controls Using Satellite Assemblies
If you need to download compiled satellite assemblies for your language and you are fine with default translations made there, use the following link:
If you decide to recompile satellite assemblies yourself.
Satellite assemblies must be signed with the same strong key token as main DevExpress assemblies. We don't distribute our key file - it's our signature. Therefore, you will be responsible for rebuilding main DevExpress assemblies if you want to compile resource files yourself. Our service provides all necessary .resx files (for the projects you modified) along with satellites assemblies. You can use these resources to rebuild satellite assemblies with your own strong key.
If you are using DevExpress 12.1 or older,
Download satellite assemblies from the Localization Service. You will receive a self-extracting archive with compiled assemblies and source files for all projects of a requested language. Unpack the files and find sources in the Sources directory.
If you are using DevExpress 11.2 or older.1. Download archive for the version of the suite you use.
Localization Servicesupports DevExpress .NET components starting with version 12.1. If you are using an older version, you can download default satellites assemblies by using the links below:
If you are using DevExpress 11.2 or older and need to modify satellites assemblies.
In case if you need to modify satellite assemblies for these outdated versions, you can use the delayed signing approach.
2. Perform necessary modifications to the *.resx files.
3. Satellite assemblies must be signed with the same strong key as DevExpress main assemblies.
In your case, after being re-built, satellite assemblies are signed with a different key (since we do not share our strong key). To solve this issue, you need to perform "delayed signing".
To extract a public key token, use the Strong Name Tool (Sn.exe): sn -e [Path to any DevExpress assembly] [Path to the output file].
Then, refer to the following articles:
Delay Signing an Assembly
How to: Delay Sign an Assembly (Visual Studio)
There are lot of projects in the downloaded archive. All of them are not ready for delay sigh building. In order to mark the DelaySign property for all projects, it is necessary to manually set this property for all projects. Download the attached ProjectsDelaySignHelper project designed to automate this routine.
Send us a partially signed assemblies and we will sign them with our strong key.
Localizing Applications in the MSDN Library
Packaging and Deploying Resources
ClickOnce Deployment and Localization
How to translate components via their Localizer objects
Show all comments