Click here to Skip to main content
15,867,568 members
Articles / Desktop Programming / WPF

WPF Localization for Dummies

Rate me:
Please Sign up or sign in to vote.
4.94/5 (64 votes)
13 Dec 2011CPOL3 min read 202.5K   4.4K   99   52
Explains how to easily localize a WPF application

Introduction

I was looking for a way to localize a WPF application and found a few solutions here on CodeProject plus a few more somewhere else. It took me quite some time to read through all of them but the end result was confusion - I could not figure out which way to go. Coming from C++ background, the resource files seemed like a logical choice so I started looking only at the resource files for the localization. It took me some time to figure it out and I realized that it's actually quite simple. The problem is, as very often the case, the documentation.
So I decided to write a beginner's article to make the localization simple, hence the name "for dummies". The goal is to explain step by step how to localize a WPF application.

Step 1

Create a WPF project. I called it, obviously, "WPFLocalizationForDummies". Note that the Properties folder has an empty resource data file named Resources.resx. Change the access modifier to Public otherwise we will not be able to use it in XAML.

Resource file

Add a string resource as shown below. We'll use this string as a main window title.

Resource file

Compile and run the project. It should run without any surprises.

Step 2

Create a localized resource file. Select Resources.resx file in the Visual Studio solution window and press Ctrl+C keys. Now press Ctrl+V keys. The copy of the Resources.resx file will be created.

Copy of the resources file

Rename "Copy of Resources.resx" file. The new name should be Resources.XX.resx where "XX" is a culture name. A culture is a combination of a specific language and country/region name and it can be found on National Language Support (NLS) API Reference page.

I suggest having an English localized resource file if you plan on supporting English language despite the fact that the default Resources.resx file may have the English strings as well. It'll be much easier later to switch to the English language and back. So our first localized resource file should be named Resources.en.resx.

English resources file

Step 3

Let's create one more localized resource file as an example, let's say Russian. Repeat step 2, the only difference is that the new file should be named Resources.ru-RU.resx.

Russian resources file

Change the value of the string "Title" to some Russian text.

Russian Resource file

Step 4

Compile the application. The compiler and linker will create a separate satellite assembly for each culture. The satellite assemblies will be placed in sub-directories under the directory holding your main assembly. The sub-directories will be named by culture, allowing the .NET runtime to locate the resources appropriate to the culture in which the application runs. The main (default) resources file will be embedded in the main assembly.

In my example, since I have 2 resource files, 2 sub-folders are created each containing the resource satellite DLL - English and Russian.

Compile output

Step 5

Set the culture in the application. It can be done explicitly as shown in the following code example.

C#
// Set the current user interface culture to the specific culture Russian
System.Threading.Thread.CurrentThread.CurrentUICulture = 
			new System.Globalization.CultureInfo("ru-RU");

Step 6

Now we have the resource DLLs, so let's use them in the application. The localized resources can be used in both XAML and C# code.

  • In XAML file:

    Add a namespace declaration to each XAML file where you'd want to use the localized resources (which is like the C# using statement).

    XML
    xmlns:p="clr-namespace:WPFLocalizationForDummies.Properties"

    In the MainWindow.xaml, replace...

    XML
    Title="Main" Height="350" Width="525">

    ...with:

    XML
    Title="{x:Static p:Resources.Title}" Height="350" Width="525">
  • In C# code, a string from the resource DLL can be retrieved as shown below:
    C#
    Title = WPFLocalizationForDummies.Properties.Resources.Title;

Conclusion

As you can see, the localization in WPF applications can be achieved very easily by following just a few steps explained above.

System Requirements

  1. Windows 7
  2. Visual Studio 2010
  3. .NET 4.0

History

  • Initial release - 12/12/2011

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Web Developer
United States United States
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.

Comments and Discussions

 
GeneralMy vote of 5 Pin
Emil Mocan23-Feb-20 23:00
Emil Mocan23-Feb-20 23:00 
QuestionNice work! Pin
Mike Hankey22-Nov-19 13:19
mveMike Hankey22-Nov-19 13:19 
PraiseMy vote of 5 Pin
Manny Mendingo8-May-17 4:26
Manny Mendingo8-May-17 4:26 
QuestionSo Simple, It's Great Pin
NoMoreComputers19-Oct-16 4:56
professionalNoMoreComputers19-Oct-16 4:56 
QuestionLocalization in DLL Pin
rozzz27-Feb-16 9:02
rozzz27-Feb-16 9:02 
QuestionGetting XamlParseException Pin
Member 1142836718-Feb-16 23:15
Member 1142836718-Feb-16 23:15 
AnswerRe: Getting XamlParseException Pin
Anathron28-Apr-16 11:36
Anathron28-Apr-16 11:36 
GeneralEasy to follow Pin
Jagd3327-Jan-16 6:35
Jagd3327-Jan-16 6:35 
GeneralRe: Easy to follow Pin
Igor Vigdorchik2-Feb-16 8:18
Igor Vigdorchik2-Feb-16 8:18 
QuestionGreat article! Pin
bugiman22-Oct-15 23:16
bugiman22-Oct-15 23:16 
AnswerRe: Great article! Pin
Igor Vigdorchik23-Oct-15 11:19
Igor Vigdorchik23-Oct-15 11:19 
GeneralIt is really suitable for everyone ! Thanks. Pin
envoy118-Sep-15 11:33
professionalenvoy118-Sep-15 11:33 
GeneralRe: It is really suitable for everyone ! Thanks. Pin
Igor Vigdorchik18-Sep-15 12:16
Igor Vigdorchik18-Sep-15 12:16 
QuestionExcellent article, but I get an error in VS... Compiling and executing are fine though. Pin
LLLLGGGG9-Sep-15 11:12
LLLLGGGG9-Sep-15 11:12 
AnswerRe: Excellent article, but I get an error in VS... Compiling and executing are fine though. Pin
Igor Vigdorchik18-Sep-15 12:20
Igor Vigdorchik18-Sep-15 12:20 
GeneralMy vote of 5 Pin
Carlos Toledo10-Dec-14 10:16
Carlos Toledo10-Dec-14 10:16 
GeneralRe: My vote of 5 Pin
Igor Vigdorchik10-Dec-14 12:25
Igor Vigdorchik10-Dec-14 12:25 
GeneralGreat Work!!! Pin
Carlos Toledo10-Dec-14 10:16
Carlos Toledo10-Dec-14 10:16 
GeneralRe: Great Work!!! Pin
Igor Vigdorchik10-Dec-14 12:25
Igor Vigdorchik10-Dec-14 12:25 
QuestionDynamic change of language Pin
F. J. H.16-Jul-14 22:36
F. J. H.16-Jul-14 22:36 
AnswerRe: Dynamic change of language Pin
Igor Vigdorchik17-Jul-14 3:17
Igor Vigdorchik17-Jul-14 3:17 
SuggestionRe: Dynamic change of language Pin
FormatException11-Aug-14 9:06
FormatException11-Aug-14 9:06 
AnswerRe: Dynamic change of language Pin
MCY20-Aug-15 22:21
professionalMCY20-Aug-15 22:21 
QuestionMy Vote is 5 Pin
Igal_Kroyter3-Jan-14 6:22
Igal_Kroyter3-Jan-14 6:22 
GeneralMy vote of 5 Pin
zlanizer2-Jun-13 17:55
zlanizer2-Jun-13 17:55 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.