Category Archives: WPF

What are benefits of PRISM?

Modular development:- As we are developing components as independent units we can assign these units to different developers and do modular parallel development. With parallel development project will be delivered faster. High reusability:- As the components are developed in individual units we can plug them using PRISM and create composed UI in an easy way.

What is PRISM?

PRISM is a framework to develop composite application in WPF and Silverlight. Composite applications are built using composition. In other words rather than building application from scratch we take prebuilt components, assemble them together and create the application. Take the below example of simple WPF UI. You can see it has lots of sections. Now rather than Continue Reading…

Explain delegate command in WPF?

First let us answer in short: – “Delegate command makes a MVVM command class independent of the view model”. Now let’s understand the long way. In MVVM architecture view talks with the view model and view model talks with the model. When actions are sent from the view they are sent to WPF commands for handling the Continue Reading…

What is the difference between MVVM and 3 layer architecture?

MVVM has an extra layer as compared to 3 layer architecture. In 3 layer architecture we have UI (view) , business logic ( model) and Data access layer ( DAL). In MVVM we have an extra layer in between view and model i.e. the view model class. 3 layer architecture complements MVVM architecture.

What is the importance of command and bindings in MVVM pattern?

MVVM in the most used architecture because of command and bindings facility provided by WPF. WPF MVVM is incomplete without command and bindings. Command and bindings helps you to connect view (WPF UI) with view model class without writing lot of behind code. Binding connects the UI input elements (textbox, combo box etc.) with the view model class Continue Reading…

What are the benefits of MVVM?

Below are the benefits of MVVM pattern:- Separation of concern: – As the project is divided in to layers, every layer handles its own responsibility. This leads to better maintenance because when we change one layer the other layer does not get affected. Increased UI Reusability: – The whole point of MVVM is to remove behind Continue Reading…

What is MVVM?

MVVM is an architecture pattern where we divide the project in to three logical layers and every layer has its own responsibility. Below are the three logical layers with explanation what they do:- View: – This layer handles responsibility of taking inputs from end user, positioning of controls, look and feel, design, visuals, colors etc. Model: – Continue Reading…