Exploring MVVM, MVC, MVP Patterns - CRB Tech

1

The Design Perspective Operator (commonly known
as MVC) structure helps you to build programs
that are make sure sustain. It consists of three
major elements, namely Design this is the
part that symbolizes the applications
data Perspective this symbolizes the
demonstration or the customer interface
layer Operator this part typically contains the
business reasoning of your application
Visit http//crbtech.in/Dot-Net-Training/
2

• MVVM-Structure
• The primary objective of the MVC style design is
  separating of issues to accomplish testability.
• The Design Perspective Operator style design
  enables you to separate the issues and creates
  your applications code simpler to make sure
  sustain. In a typical MVC style, the request
  first reaches the controller which holds the
  model with the corresponding view.
• In the MVC style design, the scene and the
  controller creates use of technique style and the
  scene and the model are synchronized using the
  viewer style. Hence, we may say that MVC is a
  substance design. The controller and the scene
  are generally combined and one controller can be
  used by several opinions. The view registers to
  the changes in the model.

Visit http//crbtech.in/Dot-Net-Training/
3
MVVM STRUCTURE
Visit http//crbtech.in/Dot-Net-Training/
4

• Model Perspective Presenter
• The MVP (Model View Presenter) style design also
  consists of three elements the model, the scene
  and the speaker. In the MVP style design, the
  Operator (in MVC) is changed by the Presenter.
  Compared with the MVC style design, the Presenter
  signifies scene due to which mocking of the scene
  is simpler and device examining of programs that
  make use of the MVP style design over the MVC
  style design are less difficult. In the MVP style
  design, the speaker manipulates the model and
  also up-dates the scene. There are two
  modifications of this style. These include the
  following.
• Inactive Perspective in this technique, the
  scene is not aware of the model and the speaker
  up-dates the scene to mirror the changes in the
  model.
• Monitoring Operator in this technique, the
  scene communicates with the model directly to
  combine information to the information manages
  without the involvement of the speaker. The
  speaker is responsible for upgrading the model.
  It manipulates the scene only if needed if you
  need a complicated customer interface reasoning
  to be implemented.

Visit http//crbtech.in/Dot-Net-Training/
5

• While both these versions promote testability of
  the demonstration reasoning, the passive view
  version is recommended over the other version
  (supervising controller) as far as testability is
  concerned primarily because you have all the
  scene modified reasoning inside the speaker.
• The MVP style design is recommended over MVC when
  you needs to provide support for several customer
  interface technological innovation. It is also
  recommended if you have complicated customer
  interface with a lot of customer connections. If
  you would like to have automated device analyze
  on the customer interface of you, the MVP style
  design is well suited and recommended over the
  traditional MVC style. If you want you can make
  your career in this field then you can join our
  .net course.

Visit http//crbtech.in/Dot-Net-Training/
6

• THANK YOU

Visit http//crbtech.in/Dot-Net-Training/