C# – the best approach to populate a masterpage control which is dependent on the content page

asp.netcmaster-pagesvb.net

I have a master page called SampleMaster.master and this page contains a Repeater control

The Repeater control will be used to display the relevant tags associated with each content page and the tags will vary between content pages

The data extraction method Tags.GetTags() is working but I do not know the best approach to populate the Repeater control in the master page dependent on what the content page is.

Would the code reside in the masterpage page code behind or the content page code behind?

Best Answer

I would suggest exposing a property or method on the child page which hands the master page the tags to display. For example

partial class myPage : IMyTaggablePage
{
    // the following is an interface member
    public List<string> GetTags()
    {
        return this.Taglist; // assuming taglist was populated somewhere on this page.
    }
}

Then on your master page you can write something like:

if (this.Page is IMyTaggablePage)
    var tags = (Page as IMyTaggablePage).GetTags();

Related Solutions

C# – How to change the background of a masterpage from the code behind of a content page

What I would do for the particular case is:

i. Define the body as a server side control

<body runat="server" id="masterpageBody">

ii. In your content aspx page, register the MasterPage with the register:

<% MasterPageFile="..." %>

iii. In the Content Page, you can now simply use

Master.FindControl("masterpageBody")

and have access to the control. Now, you can change whatever properties/style that you like!

C# – the best way to give a C# auto-property an initial value

In C# 5 and earlier, to give auto implemented properties an initial value, you have to do it in a constructor.

Since C# 6.0, you can specify initial value in-line. The syntax is:

public int X { get; set; } = x; // C# 6 or higher

DefaultValueAttribute is intended to be used by the VS designer (or any other consumer) to specify a default value, not an initial value. (Even if in designed object, initial value is the default value).

At compile time DefaultValueAttribute will not impact the generated IL and it will not be read to initialize the property to that value (see DefaultValue attribute is not working with my Auto Property).

Example of attributes that impact the IL are ThreadStaticAttribute, CallerMemberNameAttribute, ...

Best Answer

Related Solutions

C# – How to change the background of a masterpage from the code behind of a content page

C# – the best way to give a C# auto-property an initial value

Related Topic