Click here to Skip to main content
15,880,392 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;

namespace MVCSharp.Core.Configuration.Tasks
{
    #region Documentation
    /// <summary>
    /// Describes interaction point (view-controller pair). Holds a view
    /// name, the corresponding controller type and navigation information
    /// for this interaction point.
    /// </summary>
    /// <remarks><see cref="TaskInfo"/> object contains a collection of
    /// InteractionPointInfo objects, thus describing the whole task.</remarks>
    /// <seealso cref="TaskInfo"/>
    #endregion
    public class InteractionPointInfo
    {
        private string viewName;
        private InteractionPointInfoCollection navTargets = new InteractionPointInfoCollection();
        private Type controllerType;
        private bool isCommonTarget;

        #region Documentation
        /// <summary>
        /// Gets or sets the name of the view for this interaction point.
        /// </summary>
        #endregion
        public string ViewName
        {
            get { return viewName; }
            set { viewName = value; }
        }

        #region Documentation
        /// <summary>
        /// Gets descriptions for target interaction points. A view name or
        /// a navigation trigger name could be used as a key.
        /// </summary>
        #endregion
        public InteractionPointInfoCollection NavTargets
        {
            get { return navTargets; }
        }

        #region Documentation
        /// <summary>
        /// Gets or sets the type of the controller for an interation point.
        /// </summary>
        #endregion
        public Type ControllerType
        {
            get { return controllerType; }
            set { controllerType = value; }
        }

        #region Documentation
        /// <summary>
        /// If <c>true</c> then it is possible to navigate to this interaction
        /// point from any other.
        /// </summary>
        #endregion
        public bool IsCommonTarget
        {
            get { return isCommonTarget; }
            set { isCommonTarget = 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