re: B is for... BAML

Jim O'Neil — Sun, 01 Mar 2009 20:21:33 GMT

Thank you for the kind words. In terms of your question, I'm far from an expert in this area, but it's clear that at the moment locBAML is more of a "utility" that hasn't yet been brought into the mainstream of the dev process (like integration into VS), and as you can see, it requires a bit of manual effort.

Rob Relyea has a post (http://is.gd/ljP8) where there's a good discussion in the comments of locBAML and other approaches. That may help in your evaluation. Here's one for instance (http://is.gd/ljPP) that you may have already looked at. Rob's post alludes to some improvements as well, although they may not show until VS 2010, as well.

In terms of switching culture on the fly, yes you can do that. In fact the documentation for locBAML shows just that as a mechanism for testing your satellite assemblies.

re: B is for... BAML

Eddie — Sat, 28 Feb 2009 19:21:34 GMT

Hi! Nice blog you have here :) Very well written... quick question about LocBaml/Localization... do you feel this is the best, and "sanctioned" method of localization? After looking at tons (ok, maybe 7 or so...) methods and libraries that perform localization, I'm torn between which methodology to use. I'm leaning back towards the method you blogged about... Does this method easily allow a user to switch to a different language from the application? It doesn't necessarily have to be at run-time, but can they store in user-prefs, I'm using "my-MX" (Mayan Mexican... would be cool :), then at load-up, set the current culture thread to their preference?

Again, nice blog :)