How to use wpflocalizeextension in Code-Behind?

Question

How can I use wpflocalizeextension in C# code? In xaml, for getting a localized string I can use it as follows:

<Window x:Class="SomeClass"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:lex="http://wpflocalizeextension.codeplex.com"    
    lex:LocalizeDictionary.DesignCulture="uk-UA"    
   lex:ResxLocalizationProvider.DefaultAssembly="DesktopApp"    
   lex:ResxLocalizationProvider.DefaultDictionary="Resources">
   <Button Content="{lex:Loc SignInBtn}"/>

How can I get a localized string in code, for example MessageBox.Show("SignInBtn");?

Welcome to SO. Please take a moment and read [this topic](http://stackoverflow.com/help/tagging) to get informed whether you should use tags in titles or not. I'd recommend to read [all of these topics](http://stackoverflow.com/help/asking) too. — dymanoid, Jan 26 '15 at 08:50

dymanoid · Accepted Answer · 2015-01-26T09:24:47.763

13

This is pretty simple. The localization keys are stored as AssemblyName:Resources:KeyName, where Resources is the Resources class name, typically you won't change it to something other.

You can create a simple wrapper to get localized values:

using WPFLocalizeExtension.Extensions;

public static class LocalizationProvider
{
    public static T GetLocalizedValue<T>(string key)
    {
        return LocExtension.GetLocalizedValue<T>(Assembly.GetCallingAssembly().GetName().Name + ":Resources:" + key);
    }
}

So assuming you have created your string resource with the "SignInBtn" key, you can just call:

MessageBox.Show(LocalizationProvider.GetLocalizedValue<string>("SignInBtn"));

edited Jan 26 '15 at 09:24

answered Jan 26 '15 at 08:38

dymanoid

14,771
4
36
64

But you loose support for strong typed `MyProject.Properties.Resources.SignInBtn` access. – xmedeko May 21 '15 at 07:44
3

You should change the `Resources` to the file name of the resource file you use. For example `Strings` which is used in the examples. – Yusuf Tarık Günaydın May 02 '16 at 08:14
`GetCallingAssembly` can produce for you unwelcome results if u don't take care https://stackoverflow.com/a/12912473/7429464 – FindOutIslamNow Nov 29 '17 at 13:27

score 4 · Answer 2 · answered May 05 '15 at 12:33

4

I regularly use the following native command and have not encountered any errors yet:

LocalizeDictionary.Instance.GetLocalizedObject("keyComesHere", null, LocalizeDictionary.Instance.Culture).ToString()

Of course, before casting to string, you should check for null values.

answered May 05 '15 at 12:33

mcy

1,209
6
25
37

1

Passing `null` results in a `NullReferenceException` – Aug 07 '18 at 05:04

score 2 · Answer 3 · answered Jan 22 '18 at 15:41

mcy's answer worked somehow at first, but later I was getting nulls.

I would prefer to use the 3rd overload to make sure I get the right resource:

LocalizeDictionary.Instance.GetLocalizedObject("AssemblyName", "DictionaryName", "Key", LocalizeDictionary.Instance.Culture);

score -1 · Answer 4 · answered Feb 01 '19 at 19:55

-1

use it simply

Properties.Resources.yourKey

answered Feb 01 '19 at 19:55

Taran

2,895
25
22

How to use wpflocalizeextension in Code-Behind?

4 Answers4