Prism vs. MVVM Light vs. Other MVVM Framework

11-07-2009 1:10 PM |

I was wondering if anyone had a good rule of thumb when to use Prism or MVVM Light or any other MVVM Framework.

I have a large application and have all my Model Classes built and all my Views built. Now I am working on my ViewModels and getting a little deeper into commanding and such. I have looked into Prism and MVVM Light. The thing I like about MVVM Light is it is very simple for the most part and pretty much only has the MVVM features I need. But I am wondering if I should investigate more into Prism since it seems to be more widely used and I know there are a lot of people supporting it. But I don't seem to need the module and region logic for my application, mainly because we use a lot of Child Windows (actually telerik radwindows) to display detailed data so the region idea doesn't work as well in that.

 So I guess my actual questions are this:

1. Should I just use the MVVM Light framework? Or should I look more into Prism?
2. Is there a way to do more of a pop windows as regions for detail data in Prism?
3. If I went with MVVM Light could I easily transition to Prism later on if I saw the need?

Thanks and hope this isn't too vague of a question. But I would love to hear everyone's opinion on both Prism and MVVM Light or any other framework out there.