Dec 10, 2013 at 1:05 AM
Edited Dec 10, 2013 at 3:33 AM
howdy and welcome
my suggestion would be to play with both, you will find that some of the stuff they do is exactly the same but in very different manners. CM will do some things differently in some regards and generally faster for small team (even large ones) willing to learn.
CM will do LOBs just fine and probably excel doing it. Rapid development is probably one of the reasons I came over to CM from PRISM many moons ago. Part of my decision was due to the support of WPF/ WP out of the box.
Prism took a while and they leave a lot of the wire up to the views/viewmodels up to the dev, can get very repetitive, commands are one of them.
While I learned a fair amount of MVVM stuff with PRISM, it took viewmodel first coding to really appreciate the simplicity of CM to continue forward with it. Don't get me wrong everything you put in a project can be as challenging as you want it, therefore
CM can be a challenge initially as you get use to how some things are done.
CM is small in code size but with very powerful features and extensibility and would choose it over PRISM now any day. There is some code currently being refined for Portal Class Library use soon with V2.
If you need specifics don't hesitate to ask there are many knowledgeable folks lurking about.
found this site awhile after I posted this
actually a pretty good write up, as I said up top V2 is coming bringing yet another layer of flexibility with PCLs.