Click here to Skip to main content
15,881,882 members
Articles / Web Development / ASP.NET

Model View Presenter with ASP.NET

Rate me:
Please Sign up or sign in to vote.
4.93/5 (201 votes)
16 Oct 200724 min read 1.5M   27.1K   606  
This article describes using the Model-View-Presenter pattern within ASP.NET 2.0 to encourage proper separation of concerns between presentation and business logic
using System;
using System.Web.UI;
using MvpSample.Core.Domain;
using MvpSample.Presenters;
using MvpSample.Presenters.ViewInterfaces;

public partial class Views_EditCustomerView : UserControl, IEditCustomerView
{
    /// <summary>
    /// Provides a means for setting/retrieving the <see cref="Customer" /> to be updated.
    /// Arguably, you could just pass primitives back and forth instead of having the view
    /// be bound to the domain layer...but passing primitives could become quite painful
    /// very quickly.  IMO, the benefits of brevity outweigh the "disadvantages" of 
    /// being dependent on the domain layer.
    /// </summary>
    public Customer CustomerToUpdate {
        get {
            Customer updatedCustomer = new Customer(txtCompanyName.Text);
            updatedCustomer.ID = hidCustomerID.Value;
            updatedCustomer.ContactName = txtContactName.Text;
            return updatedCustomer;
        }
        set {
            if (value == null) throw new ArgumentNullException("CustomerToUpdate may not be null");
            
            hidCustomerID.Value = value.ID;
            lblCustomerID.Text = value.ID;
            txtCompanyName.Text = value.CompanyName;
            txtContactName.Text = value.ContactName;

            grdOrders.DataSource = value.Orders;
            grdOrders.DataBind();
        }
    }

    public void AttachPresenter(EditCustomerPresenter presenter) {
        this.presenter = presenter;
    }
    
    protected void btnUpdate_OnClick(object sender, EventArgs e) {
        // Instead of having the presenter grab the updated customer via the CustomerToUpdate's getter,
        // you could also pass the updated Customer directly to the UpdateCustomer method.  I prefer
        // the consistency of using the getter/setter pair.
        presenter.UpdateCustomer(Page.IsValid);
    }

    protected void btnCancel_OnClick(object sender, EventArgs e) {
        presenter.CancelUpdate();
    }
    
    private EditCustomerPresenter presenter;
}

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


Written By
Web Developer
United States United States
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.

Comments and Discussions