Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
Easy pattern give you flixibilty to design same VM for difrent views , and it give your team flixibility to work togther in same time , also adding unit test.
It's a design pattern makes the project clean and easy to develop by separate:
1. The view (with an empty code behind) that's help us to create a cross-platform apps with one solution and multiple views.
2. The view-model that's controls the view and communicate with it using the binding technics and that's help us to create a unit-test tests.
3. The model or the data access that's have all repositories and services to get/set the data form/to the database.
hhuooojjjjkkkkkkkjjjjjhhjj
WPF ? Windows Presentation Foundation
MVVM ?Model-View-ViewModel
The Model-View-ViewModel (MVVM) pattern helps you to cleanly separate the business and presentation logic of your application from its user interface (UI).
MVVM stand for Model View ViewModel in WPF. it is three layer Architecture from developing Application. View is used for presentation of application.it consist on xaml. Second layer ModelView consist on business logic of application using c# or visual basic. The third layer is Model which used for interaction with database.
Its a Model-View-ViewModel (MVVM) is an architectural pattern used in software engineering that originated from Microsoft which is specialized in the Presentation Model design pattern. It is based on the Model-view-controller pattern (MVC), and is targeted at modern UI development platforms (WPF and Silverlight) in which there is a UX developer who has different requirements than a more "traditional" developer. MVVM is a way of creating client applications that leverages core features of the WPF platform, allows for simple unit testing of application functionality, and helps developers and designers work together with less technical difficulties.
MVVM - MVVM is an architectural pattern used to developing WPF application.
Its full name is Model - View - ViewModel.
Model - Represents the Object Oriented Approch. It represents the Data Access Layer.
View - View represents the appearence. Designer part in the architectural pattern
ViewModel - ViewModel does the same role as the controller does in MVC.