Summary
I want to clarify a common misunderstanding I've seen in the NET communities in the past years, about using and working with the presentation patterns in general. A presentation pattern is adopted in order to loosely couple the UI logic from the presentation logic and to make the presentation part of the application more testable and flexible. It is not used to separate the domain from the UI; this is not the primary reason for adopting presentation patterns.
Presentations pattern such MVP and MVVM are only part of the UI; they don't represent the overall solution for UI architecture. With a presentation pattern, you should solve some specific aspects of the UI layer but this doesn't mean that you need a third-party framework or a personal ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access