This project is read-only.

How is this different from Prism?

Aug 18, 2009 at 8:32 AM

And why use this over Prism?  aka  Composite WPF from P&P.

Aug 18, 2009 at 5:45 PM

Prism exists to help developers create composite applications with WPF.  MVVM Foundation does not have such a lofty agenda.  My library certainly has some functional overlap with Prism, but that is about all they have in common.  Most MVVM apps that I work on end up using the same core set of classes, so I decided to package them up into a library and share it with others.  If you prefer the Prism way of doing things, then by all means go with Prism.

Aug 18, 2009 at 8:32 PM

thanks for the info.  yeah, its not about a preference one way or another, just important to understand the differences and purposes.  There is always a place for things.  Prism may be overkill where MVVM Foundation may be the perfect fit (and much more simple to grasp I imagine).   Either way, Prism wouldnt be able to function without implementing MVVM I think, and is has things like eventing, etc, so thats what sparked the curiosity here.  Cool stuff.