Model View Presenter And Its Best Practices

• Download MVP_Demo_src - 28.07 KB

Introduction

With the advent of newer technology and framework, architecture design has become very important for development of application.Utilization of the same business functionality across platform based Web application and smart client needs a tactful architecture.Another challenge has been to fit in unit testing framework with the application. MVC failed to achieve this. MVP proved to be boon to achieve this milestone.

MVP vs. MVC

Demerits of Model View Controller

Why MVP ?

Logical Architecture

Physical Architecture

Best Practices:

Data Access Layer

ClientLookupDataProvider.cs
		partial public class DataProvider
		{
        }
        

Service Layer

Presenter Layer:

  public class BasePresenter
       {
           public IServiceProvider m_Service=null;
           public BasePresenter()
		   {
				m_Service=new Services.ServiceProvider()
		   }
		   public void ProcessPresenterLayerException()
		   {
		   }
	  }
	  

Public void LoadCustomerList()
{ 
    Ilist customerList = new list(); 
    customerList = GetCustomerList(m_View.CustomerID){}
} 
Public void SortCustomerList(){}
Public void PagingCustomerList(){}

Private IList GetCustomerList(int customerID){}

Domain: Business Entity

private int _demandID = int.MinValue;
private string _demandName = string.Empty;

Public Sample (int a, int b, int c): base (a)
{
……
}
public Sample(int a, int b, int c, int d):this(a,b,c)
{
..
}

References