Programming Patterns & Practices
how to build an outlook style application with prism v2 – Part 2 - Erwin van der Valk's blog: Practicing patternsA while ago, I put an example application on my blog on how to build an outlook style application .
[Update] This is part 1 of this post.
Prism 4.0 includes guidance in several new areas, resulting in new code in the Prism Library, new and updated QuickStarts, a new reference implementation, and updated documentation. Parts of the Prism Library changed between Prism 2.0 and Prism 4.0 to support the new guidance, fix existing issues, and respond to community requests.
Prism provides guidance designed to help you more easily design and build rich, flexible, and easy-to-maintain Windows Presentation Foundation (WPF) desktop applications, Silverlight Rich Internet Applications (RIAs), and Windows Phone 7 applications. Using design patterns that embody important architectural design principles, such as separation of concerns and loose coupling, Prism helps you to design and build applications using loosely coupled components that can evolve independently but that can be easily and seamlessly integrated into the overall application. These types of applications are known as composite applications.
This chapter addresses what needs to happen to get a Prism application up and running.
Applications based on the Prism Library are composite applications that potentially consist of many loosely coupled types and services.
The Model-View-ViewModel (MVVM) pattern helps you to cleanly separate the business and presentation logic of your application from its user interface (UI).
An application user interface (UI) can be built by using one of the following paradigms:
As the user interacts with a rich client application, its user interface (UI) will be continuously updated to reflect the current task and data that the user is working on. The UI may undergo considerable changes over time as the user interacts with and completes various tasks within the application. The process by which the application coordinates these UI changes is often referred to as navigation .
When building large complex applications, a common approach is to divide the functionality into discrete module assemblies. It is also desirable to minimize the use of static references between these modules.
To successfully move a Prism application into production, you need to plan for deployment as part of the design process of your application.
So... in case anyone comes across this thread, here's what I wound up with. To add items to the options dialog, a module creates a class or classes that export IOptionsProvider.
patterns & practices Developer Center February 2012
Patterns WPF Apps With The Model-View-ViewModel Design Pattern Josh Smith
With Microsoft WPF technology, a new pattern is born and is going to be called MVVM (Model View ViewModel).