Microdoft WPF

The following .NET file types with WPF resources can be localized with RC-WinTrans:

  • EXE and DLL (.NET application assembly files)
  • XAML (WPF window files)

WPF Support in RC-WinTrans

Since 2011 and Version 9.1, WPF resources in .NET assembly files can be translated / localized in RC-WinTrans as "true" WPF. This means that the complete source data from a WPF assembly (EXE or DLL)- including WPF windows, menus and images- will be read, presented and rendered for translation with RC-WinTrans.

RC-WinTrans handles WPF just like other .NET applications- no special preparation or conversion is required. For multi-lingual .NET applications RC-WinTrans will create translated .NET satellite assembly DLLs, one for each target language (the same as other .NET assemblies based on Forms resources (RESX).

Figure 1:  The "Project Data" tree view of RC-WinTrans (left) where a WPF assembly "WPFAppl.exe" has been added to
the active project. The resources tree has been expanded to show the individual resources of the "Window3.baml" file
in the application (EXE) file. On the right the translatable text of the "Window3.baml" file is listed in the "Text Table" view.

RC-WinTrans makes the following display / editing options available for WPF data:
  • "Text Table" view / "Translation Edit" bar.
  • "Menu" view (for menu resources).
Developer info:  RC-WinTrans does NOT require WPF resources to be prepared (with MSBuild.exe) in such a way that all items are given the ID "x:Uid." RC-WinTrans uses the "Name" attribute to identify an item in the translation process, and only uses an "x:Uid" attribute value if "Name" does not exist.