Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Community Module idea: MonkeyFinder MVP-VM decoupled application following best P&P #79

Open
BillKrat opened this issue Jul 30, 2022 · 0 comments

Comments

@BillKrat
Copy link

Refactor existing Monkey Finder application for decoupled architecture. The Model-View-Presenter, View-Model (MVPVM) pattern follows best practices as outlined by the Microsoft Application Architecture Guide for decoupled applications using inversion of control, aka dependency injection.

Decoupled applications promote reuse of views, view models, business logic and data access layers with other modules and/or applications as they are not tightly coupled to other components. Decoupled applications are more easily architected, updated, and maintained - if you understand the patterns.

Part 0 - Overview (understanding the patterns).
Part 1 - Wiring up a decoupled framework
Part 2 - MVPVM
Part 3 - Event Aggregation (communication between layers/components)
Part 4 - Navigation
Part 5 - Adding a new module (reuse of existing components)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant