WPF frameworks: Which one should I prefer?

Question

There is a similar question already asked at SO: http://stackoverflow.com/questions/1409553/what-framework-for-mvvm-should-i-use

But what I would like to know is whether any of these WPF frameworks are actually production ready?

I really don't want to use any framework which is not well supported or are just half baked attempts. And by saying so, I don't wanna undermine the individual efforts put into the creation of these frameworks.

It would be great if you can tell which framework you have "used" and/or your opinions regarding it.

Is Microsoft planning to release any such framework? There attempt with "MVVM Toolkit" was not so impressive.

Answer 1

MVVM is a patterns/practices thing more than anything else. As with all patterns and practices (including things like Data Access Layers, Repository Patterns and such), you can always roll your own.

Given this, and the fact that Josh Smith's framework (MVVM Foundation) is the basis for some of the other frameworks, I would start with his, and move to a more sophisticated framework if the need arises.

Because of it's limited scope, and the fact that it has been around for awhile, and the fact that the author is an expert, this framework is likely to be more mature than the others.

Answer 2

Microsoft's MVVM Toolkit is an early alpha release. They opened it up to the WPF Disciples to have a look at, and it was heavily critiqued, but MS have listened to this criticism and are going to build features back in based on the discussions.

Don't be afraid to look into Ocean - Karl's framework. He has huge amounts of experience in MVVM, and his work has influenced Josh as much as Josh has influenced him.

To be honest, you're going to have to download them and have a play around with them. Only you can work out whether or not they fit well with what you're trying to do.

Answer 3

Caliburn is production ready. It is used in production in fact, for example in NHProf.