Out of interest, do any of you find yourself localizing non-string resources?
Strangely enough, not in WPF and only once in SL4 where the company logo had to change in the screen header. For the latter I read a customer config file with the Uri of the image they want (placed in a known folder) and it bound to a Theme class for the customer, so it's just standard boring binding. Ooops! I forgot to mention the key part of my SL4 globalisation trick in the previous post. When a control loads I use the tree helper class to walk all the way down the control tree looking for controls with a Name and Text/Content/ToolTip/etc properties and I use the Name to see if the property should be set from a resx lookup. This Load-Loop-Lookup-Replace technique is something I used in the WinForms years, and it works well for a small amount of coding. It also works well in the SL4 app, but as I mature ;-) I get more of an uneasy feeling about it and I prefer to work in more standard ways. That's why I didn't use the technique in my WPF app and decided to try and use Binding and markup extender techniques. Greg
_______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
