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.5K   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>
    /// Used to declare navigation triggers with targets for interaction points.
    /// </summary>
    /// <remarks>Should be used with <see cref="TaskInfoByAttributesProvider"/> or
    /// <see cref="DefaultTaskInfoProvider"/> task info providers. They
    /// convert this attribute occurrences into <see cref="TaskInfo"/>
    /// objects.</remarks>
    /// <example>
    /// Below we declare a task with two interaction points and a "Next" trigger
    /// navigating from "View 1" to "View 2":
    /// <code>
    /// class MyTask : TaskBase
    /// {
    ///     [InteractionPoint(typeof(MyController))]
    ///     [NavTarget("Next", View2)]
    ///     public const string View1 = "View 1";
    /// 
    ///     [InteractionPoint(typeof(MyController))]
    ///     public const string View2 = "View 2";
    /// 
    ///     public override void OnStart(object param)
    ///     {
    ///         Navigator.NavigateDirectly(View1); // Initial interaction point is "View 1"
    ///         Navigator.Navigate("Next"); // Navigate to "View 2"
    ///     }
    /// }
    /// </code>
    /// </example>
    #endregion
    [AttributeUsage(AttributeTargets.Field, AllowMultiple = true)]
    public class NavTargetAttribute : Attribute
    {
        private string triggerName;
        private string viewName;

        #region Documentation
        /// <summary>
        /// Contructor taking the trigger name and the view name of the
        /// target interaction point.
        /// </summary>
        #endregion
        public NavTargetAttribute(string triggerName, string viewName)
        {
            this.triggerName = triggerName;
            this.viewName = viewName;
        }

        #region Documentation
        /// <summary>
        /// The name of the trigger initiating the transition.
        /// </summary>
        #endregion
        public string TriggerName
        {
            get { return triggerName; }
            set { triggerName = value; }
        }

        #region Documentation
        /// <summary>
        /// The view name for the target interaction point.
        /// </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