Home/ Questions/Q 6822937
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T21:43:23+00:00

I followed the tutorial on msdn about localization, and they implement localized bindings like

  • 0

I followed the tutorial on msdn about localization, and they implement localized bindings like this:

{Binding Path=Localizedresources.AppName, 
         Source={StaticResource LocalizedStrings}}

But when I work with Expression Blend localized bindings are implemented like this:

{Binding Localizedresources.AppName, Mode=OneWay}

I don’t understand why they are different. Is there a reason why MSDN and Expression Blend do it differently? Is there a reason why I should prefer one way over another?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The former is the implementation for Windows Phone, as Windows Phone don’t support static class bindings (as opposed to WPF).

    The latter is for WPF, and shouldn’t work in Windows Phone.

    Also, if you want Expression Blend support for your localization, add the LocalizedStrings resource to the DesignTimeResources.xaml file (typically located in the Properties folder). Then once you build your project, Expression Blend will show the localization at design-time as well.

    • 0