Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Does the introduction of WPF deprecates the Windows Forms Resources in any way?
With Windows Forms Resources we could:
Since I haven’t found an easy way for consuming those resources directly from the XAML, I suppose there is an alternative which works better with WPF. Is that so?
Embedded images work very easily in WPF. Just add the image to your Solution (with a type of Resource), and WPF can reference it from XAML, pulling it out of the resources directly. This is completely seamless.
Internationalization is a bit trickier, though. You can internationalize strings using resource files, just like in Windows Forms. However, strings within XAML are not handled the same way. There are two approaches to internationalization in WPF – both of which require a bit more effort than Windows Forms. However, there is a lot more flexibility and power in WPF internationalization.
First, you can use a markup extension to internationalize a string in WPF. This requires some custom plumbing to be written, but works more like the Windows Forms approach.
The more powerful approach is to actually load different XAML based on the region. This allows you to not only change your strings, but also adapt your UI layout – hence the extra power and flexibility (at the cost of more design time).