Click here to Skip to main content
11,412,125 members (65,505 online)
Click here to Skip to main content
Add your own
alternative version

Model View Presenter via .NET

, 10 Oct 2009 CPOL
An article outlining an implementation of the Model View Presenter pattern in .NET, contrasting it with existing implementations of MVP, MVC, and using co-dependant interfaces to allow for abstract coordination.
ExampleProject.zip
ExampleProject.Contracts
bin
Debug
CobaltSoftware.Foundation.ModelViewPresenter.dll
ExampleProject.Contracts.dll
Properties
ExampleProject.Model
bin
Debug
CobaltSoftware.Foundation.ModelViewPresenter.dll
ExampleProject.Contracts.dll
ExampleProject.Model.dll
Properties
ExampleProject.Presenters
bin
Debug
CobaltSoftware.Foundation.ModelViewPresenter.dll
ExampleProject.Contracts.dll
ExampleProject.Presenters.dll
Properties
ExampleProject.Views
bin
Debug
CobaltSoftware.Foundation.ModelViewPresenter.dll
ExampleProject.Contracts.dll
ExampleProject.Views.dll
Properties
CobaltSoftware.Foundation.ModelViewPresenter
bin
Debug
CobaltSoftware.Foundation.ModelViewPresenter.dll
Core
Properties
Support
ExampleProject.Application
bin
Debug
CobaltSoftware.Foundation.ModelViewPresenter.dll
ExampleProject.Application.exe
ExampleProject.Application.vshost.exe
ExampleProject.Application.vshost.exe.manifest
ExampleProject.Contracts.dll
ExampleProject.Model.dll
ExampleProject.Presenters.dll
ExampleProject.Views.dll
Properties
Settings.settings
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace CobaltSoftware.Foundation.ModelViewPresenter
{
    /// <summary>
    ///     The IView interface defines a passive view in the Model-View-Presenter
    ///     pattern. The view registers itself with a presenter (as controlled by
    ///     an orchestration mechanism) and requests it's state. The view should
    ///     expose events that are consumed by the presenter for observation and 
    ///     change tracking in response to interactions.
    /// </summary>
    /// <remarks>
    ///     <para>
    ///         <list>
    ///             <listheader>Version History</listheader>
    ///             <item>10 October, 2009 - Steve Gray - Initial Draft</item>
    ///         </list>
    ///     </para>
    ///     <para>
    ///         This implementation uses self-constrained generics to allow
    ///         bi-directional strong coupling of interface types for both
    ///         presenter and view, allowing mutual strong references.
    ///     </para>
    /// </remarks>
    /// <typeparam name="TViewContract">View contract type</typeparam>
    /// <typeparam name="TPresenterContract">Presenter contract type</typeparam>
    public interface IView<TViewContract, TPresenterContract>
        where TViewContract : IView<TViewContract, TPresenterContract>
        where TPresenterContract : IPresenter<TPresenterContract, TViewContract>
    {
        /// <summary>
        ///     Attach this view to a presenter.
        /// </summary>
        /// <param name="presenter">Presenter instance</param>
        /// <param name="requiresInitialState">Does this view require initial state to be pushed in?</param>
        /// <remarks>
        ///     <para>
        ///         Note that this is the initiating action for view/presenter
        ///         wireup. This method should, in turn, cause the view to call
        ///         ConnectView on the presenter. The ConnectView, conversely
        ///         will inspect the Presenter property of the view to ensure
        ///         that the two are in agreement (preventing the operation
        ///         occuring in reverse).
        ///     </para>
        ///     <para>
        ///         If the view is already attached to another presenter then
        ///         the view will be detached from that presenter first and
        ///         fire the appropriate disconnect events, before attempting
        ///         to connect to the new view.
        ///     </para>
        ///     <para>
        ///         If attempting to-reattach to its existing presenter there is
        ///         no work carried out (i.e. initial connection events do
        ///         not fire again).
        ///     </para>
        /// </remarks>
        void AttachToPresenter(TPresenterContract presenter, bool requiresInitialState);

        /// <summary>
        ///     Detatch from any current presenter.
        /// </summary>
        /// <remarks>
        ///     <para>
        ///         This is the initiating operation for disconnection. A view
        ///         has this method called, which will in turn cause DisconnectView
        ///         to be called on the presente.r
        ///     </para>
        ///     <para>
        ///         If the view is not attached to any presenter then this is
        ///         a null operation with no effect/error.
        ///     </para>
        /// </remarks>
        void DetatchFromPresenter();
        /// <summary>
        ///     Presenter this view is associated with.
        /// </summary>
        TPresenterContract Presenter { get; }
    }
}

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, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Steven James Gray
Software Developer (Senior) Insurance Industry
United Kingdom United Kingdom
Steve Gray is a Senior Developer at a British insurance company, working on a popular aggregator. When he's not writing ASP .NET, it's because there's SQL or WCF to write instead.

| Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.150414.5 | Last Updated 10 Oct 2009
Article Copyright 2009 by Steven James Gray
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid