Apr 30, 2015 at 11:24 AM
Edited Apr 30, 2015 at 11:37 AM
My question is somewhat really basic about prism. Hence, kind request to don't underrate it. Rather, it would be great to know the answers which helps me to take a great step in my very important project of my student career.
- What is prism?
Separate Framework? or it is added to the existing .NET Framework or is it just a libraries which I can use by just referencing them while coding my WPF MVVM project?
- Is prism selection good in my business case? ( just want to know i am right ? and looking for suggestions)
I have to develop a WPF MVVM application to visualize the machine data of the machine manufacturing company. Hence, my project is a data visualization project. So, I may have to use graphs, charts histograms etc. in order to display my analysed data.
Note: The target device to run application would be tablets, Windows pro books.
Now, while I was reading about prism. I somewhere encountered saying that, you have to use prism if its a case of data visualization project. Now, what is this "Use Prism" mean?
I hope those who read this is able to understand confusions and doubts that I am presently undergoing. Hence, It would be great, if, anyone can please answer based on the questions posed above.
Thank you very much
While some would call Prism a framework, at the end of the day it is just a set of class libraries that help you implement a number of design patterns in WPF, Windows Store, and Phone apps.
For your use case, yes, Prism is a great start for implementing an app using the MVVM pattern. It also addresses a number of other patterns that you can optionally use including modularity and UI composition with Regions. There are features for Navigating between
views, communicating between views and other things.
Best place to start if you have Pluralsight access is with Brian Lagunas' course:
, followed by his course on Prism 5:
. If you don't have access, shoot me a note brian.noyes on gmail and I can get you a one month trial.
You can also check out the book that I am co-author on that is available in MSDN:
Also, start following us at
, because the project is being carried forward as an open source project there.