![]() ![]() ![]() There have been a number of other articles on this subject, including Localizing WPF Applications using Locbamlwhich covered different methods of localizing XAML files, each with their own advantages and disadvantages. This update removes the need for this wrapper, making this much easier to use. The original implementation presented in this article required a wrapper class around the set of properties, which was a hassle to either manually or auto-generate. The example application has a few localized strings to show it working, but since there’s only so many ways to demonstrate localized strings, I’ve kept it brief. Keep design-time support for localized elements working in Expression Blend (and hopefully other XAML design applications).Use the existing Resource file structure ( *.resx files), which can be maintained in Visual Studio.Switch cultures at runtime – automatically updating all localized elements.In this case, I also wanted to be able to: This article is yet another attempt to address the problem of localizing WPF applications in a simple and maintainable fashion. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |