Click here to Skip to main content
15,887,175 members
Please Sign up or sign in to vote.
4.00/5 (1 vote)
See more:
Hi,
we are going to develop a project in WPF which must have following functionalities
Secured
Consistence
Maintainence Free
Modularity
Easily Changeable Code

We already have develop a project in WPF using MVVM pattern, but it really gets difficult some time to manage it, mostly due to event handling between modules & some what dependency of views & modules on each other.
Hence after some research i came across PRISM using UNITY & found it quiet easy to use.

Also on my research ahead i came across MVVM Light & Caliburn micro, which many people have recommended more over PRISM, but i was unable to get any proper reason on it.
Only thing i got to know is that in MVVM Light, it has IMessenger which is must fast & reliable than Event Aggregator in PRISM. However MVVM Light does not have any alternate for Regions in PRISM

Hence what i exactly want to know is:
1) Advantages & Disadvantages of MVVM Light over PRISM (MVVM Light vs PRISM)
2) Advantages & Disadvantages of Caliburn over PRISM (Caliburn vs PRISM)
3) Caliburn vs MVVM Light
4) Which one is better for a large application?
5) If I select PRISM than what should be used, UNITY, MEF Or Reactive UI?

What I have tried:

I have gone through some of this links
MVVM, Unity, Prism, MEF, Caliburn - What should I use?

7 Things You Need to Know Before Starting a Prism WPF Project

prism vs mvvm light for wpf
Posted

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900