Click here to Skip to main content
15,885,366 members
Articles / Programming Languages / C#

Building an MVP Framework for .NET. Part 4: Strongly Typed Associations

Rate me:
Please Sign up or sign in to vote.
4.86/5 (4 votes)
25 Apr 2008Ms-PL2 min read 27.4K   339   31  
In this article we continue developing a Model-View-Presenter framework for .NET platform. The new features we are implementing here are strongly typed asscoiations between controllers, views and tasks for higher convenience and type safety.
//===========================================
// MVC# Framework | www.MVCSharp.org        |
// ------------------------------------------
// Copyright (C) 2008 www.MVCSharp.org      |
// All rights reserved.                     |
//===========================================

using System;
using System.Text;
using MVCSharp.Core.Configuration.Views;

namespace MVCSharp.Winforms.Configuration
{
    #region Documentation
    /// <summary>
    /// Instances of this type describe views within the Windows Forms
    /// presentation platform. In addition to the view type it intoduces
    /// several properties specific to the Windows Forms presentation
    /// mechanism.
    /// <para>When the <see cref="WinformsViewsManager"/>activates a view
    /// it looks to the properties of the corresponding WinformsViewInfo
    /// object. For example a form will be shown as modal if
    /// <see cref="WinformsViewInfo.ShowModal"/> is set to true.</para>
    /// </summary>
    #endregion
    public class WinformsViewInfo : ViewInfo
    {
        private bool showModal;
        private bool isMdiParent;
        private string mdiParent;

        #region Documentation
        /// <summary>
        /// Constructor recieving the view name and type as parameters.
        /// </summary>
        #endregion
        public WinformsViewInfo(string viewName, Type viewType) : base(viewName, viewType)
        { }

        #region Documentation
        /// <summary>
        /// Specifies if a view should be displayed as a modal dialog.
        /// </summary>
        #endregion
        public bool ShowModal
        {
            get { return showModal; }
            set { showModal = value; }
        }

        #region Documentation
        /// <summary>
        /// Specifies whether a view should act as an MDI parent form.
        /// </summary>
        #endregion
        public bool IsMdiParent
        {
            get { return isMdiParent; }
            set { isMdiParent = value; }
        }

        #region Documentation
        /// <summary>
        /// Specifies an MDI parent view name.
        /// </summary>
        #endregion
        public string MdiParent
        {
            get { return mdiParent; }
            set { mdiParent = value; }
        }
    }
}

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 Microsoft Public License (Ms-PL)


Written By
Team Leader
Russian Federation Russian Federation
Oleg Zhukov, born and living in Russia is Lead Engineer and Project Manager in a company which provides business software solutions. He has graduated from Moscow Institute of Physics and Technology (MIPT) (department of system programming) and has got a M.S. degree in applied physics and mathematics. His research and development work concerns architectural patterns, domain-driven development and systems analysis. Being the adherent of agile methods he applies them extensively in the projects managed by him.

Comments and Discussions