Karl Shifflett and I have been hard at work on a WPF Wizard application that is fully globalized and localized. I just published an article about it on CodeProject, and am extremely happy with how it turned out. If you’re interested in reading it, here’s the link:

There was a very long and interesting thread about MVVM today amongst the WPF Disciples. The thread started out with a simple thought: using a ViewModel eliminates most scenarios where value converters are necessary. My point was that a ViewModel class is essentially a value converter on steroids, thus rendering the IValueConverter interface irrelevant for most bindings.

This comment lead to a very engaging discussion about peoples’ fundamental philosophies regarding how a well-designed WPF application should be built. Some people strongly disagreed with me, and gave lucid explanations of why. It was a real eye-opener for me to have fellow MVVM advocates express opinions that, while completely valid and reasonable, are strikingly different from my own.

The thread even took a brief detour into something I’ve been thinking about for a while now but never publicly discussed: MMVVVVM! Yeah, I know, that’s a terrible name for a design pattern…

If this sort of thing interests you, I highly suggest you set aside some time to read this thread. What are your thoughts about this?