WPF localization with multiple Resource.resx files (resource managers) used for one language. Useful for localizing Prism modules.
Clone or download
Latest commit dfb5c2b Dec 28, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
LICENSE Initial commit Dec 23, 2018
README.md Update README.md Dec 28, 2018
WpfLocalizationWithMultipleResourceManagers.cs Add files via upload Dec 28, 2018


WPF localization with multiple Resource.resx files (resource managers) used for one language.

If you only want to localize text and you find the WPF Localization Extension too large for your needs, you can use this as a "one file" alternative that can localize strings (but not images).

It supports dynamic changes of culture, that means: it allows changing language at run-time, without restarting the application.

Useful for localizing multiple Prism modules:



This solution is based on the excellent simple approach by Jakub Fijałkowski

His solution can be found on GitHub

The hard coded reference to the ResourceManager was replaced with a Dictionary.

The markup extension is still used in the same way:

<TextBlock Text="{loc:Loc MyText}"/>

A new attached property Translation.ResourceManager is used with the root control of the visual tree (e.g. UserControl) to set the ResourceManager for the localization markup extension:

<UserControl xmlns:resx="clr-namespace:MyProject.Properties"
             loc:Translation.ResourceManager="{x:Static resx:Resources.ResourceManager}">
    <TextBlock Text="{loc:Loc MyText}"/>

If you want to use a different ResourceManager with a specific control you can override the root setting at the control level:

<TextBox loc:Translation.ResourceManager="{x:Static resx:Resources.ResourceManager}" Text="{loc:Loc MyText}"/>

If you want to use the markup extension inside a control template you have to set the Translation.ResourceManager attached property on the TemplatedParent.

If you use this solution in a separate class library

  • Visual Studio designer displays the FallbackValue that was added to LocExtension.

  • You have to change Resources access modifier from "internal" to "public".

You can do this by setting the Custom Tool property in the Property Window for the Resx file: use the PublicResXFileCodeGenerator instead of the ResXFileCodeGenerator.

Alternatetively you can set the Access Modifier to public when you open the resx file in Visual Studio. The Access Modifier dropdown box can be found at the top of the form.