Click here to Skip to main content
15,886,676 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.Views
{
    #region Documentation
    /// <summary>
    /// A base attribute for declaring views. See example code below.
    /// </summary>
    /// <remarks>
    /// ViewAttribute attributes are converted to <see cref="ViewInfo"/> objects
    /// by an instance of the <see cref="MVCConfiguration.ViewInfosProviderType">
    /// MVCConfiguration.ViewInfosProviderType</see> type.
    /// <para>Note that different presentation mechanisms
    /// may require different ViewAttribute descendants to
    /// declare views. For instance see <see cref="MVCSharp.Winforms.Configuration.WinformsViewAttribute"/> and
    /// <see cref="MVCSharp.Webforms.Configuration.WebformsViewAttribute"/> attributes.</para>
    /// </remarks>
    /// <example>
    /// Below we declare a view type that should be used for the <c>MyTask.MyView</c>
    /// view within the <c>MyTask</c> task.
    /// <code>
    /// [WinformsView(typeof(MyTask), MyTask.MyView)]
    /// class MyView : IView
    /// {
    ///     ...
    /// }
    /// </code>
    /// </example>
    /// <seealso cref="MVCSharp.Winforms.Configuration.WinformsViewAttribute"/>
    /// <seealso cref="MVCSharp.Webforms.Configuration.WebformsViewAttribute"/>
    #endregion
    [AttributeUsage(AttributeTargets.Class, AllowMultiple = true)]
    public class ViewAttribute : Attribute
    {
        private Type taskType;
        private string viewName;

        #region Documentation
        /// <summary>
        /// Parameterless constructor.
        /// </summary>
        #endregion
        public ViewAttribute()
        {
        }

        #region Documentation
        /// <summary>
        /// Constructor which sets TaskType and ViewName taking
        /// values from parameters.
        /// </summary>
        #endregion
        public ViewAttribute(Type taskType, string viewName)
        {
            TaskType = taskType;
            ViewName = viewName;
        }

        #region Documentation
        /// <summary>
        /// Links an attribute to a specific task type.
        /// </summary>
        #endregion
        public Type TaskType
        {
            get { return taskType; }
            set { taskType = value; }
        }

        #region Documentation
        /// <summary>
        /// Links an attribute to a specific view within a task.
        /// </summary>
        #endregion
        public string ViewName
        {
            get { return viewName; }
            set { viewName = 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