Let me firstly describe the localisation support in WPF – absolute pants
For those people who might read this who don’t understand the local London, UK colloquial term pants – it simply means very bad.
Essentially you get the same localisation engine as v2.0 Windows Forms without the design time support. Therefore you can generate csv files for each different culture, edit them, maintain them and recompile to be able to switch languages. It’s a bit horrible though.
Alternatively you can maintain resources for each culture in resource files and bind to them.
There is a good article on code project which describes the three methods localisation in WPF:
VS2008 doesn’t seem to address this either, so I would like the boys and girls in Redmond (et al) to attack this with the same verve as they did the ORM problem. They came up with such a great solution for that, that I don’t think it has sunk in yet just how great it will prove to be.