This question is inspired from this closed question:
What does Prism actually offer the developer? And is it worth it?
I have already implemented my own custom MVVM implementations in enterprise applications. I am interested in knowing:
I hope this question is not subjective and everyone please don't get into arguments:)
As with many frameworks that do a common task for you, you get:
PRISM can be interesting to you because it's more than an MVVM framework. Yes, a part of it can be considered in fact an MVVM framework (the NotificationObject
, the EventAggregator
and the Command objects are all examples of that), but it offers much more.
It allows you to create Composite Application of multiple loosely couples "Modules". It has a very flexible and extensible navigation framework (Region Navigation), offers integration with IoC containers (notably Unity and MEF) and a ton of other features.
Other than that, the documentation (including an ebook) is pretty good and comes with a lot of examples and quick starts. I believe it's worth the investment, which shouldn't be much, by the way.
Hope this helps:)
Prism is an application composition framework with MVVM features, but is not (in my opinion) a fully-featured MVVM framework. It offers the minimum required to do some basic MVVM development.
See my previous answer to a similar question for a breakdown of application composition frameworks and MVVM frameworks. Most applications pick one from both categories:
With prism and MEF you can build highly extensible and maintainable. Net application. With each module with its own UI in its own separate dll. The only connection between your modules or extensions and MainUI will be region in which you will inject the UI of your extension. And believe me it's highly extensible and maintainable
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.