views:

1134

answers:

2

I'm working on a .net 3.5 site, standard website project.

I've written a custom page class in the sites App_Code folder (MyPage).

I also have a master page with a property.

public partial class MyMaster : System.Web.UI.MasterPage
{
...
    private string pageID = "";

    public string PageID
    {
        get { return pageID; }
        set { pageID = value; }
    }
}

I'm trying to reference this property from a property in MyPage.

public class MyPage : System.Web.UI.Page
{
...
        public string PageID
        {
            set
            {
                ((MyMaster)Master).PageID = value;
            }
            get
            {
                return ((MyMaster)Master).PageID;
            }
        }
}

I end up with "The type or namespace name 'MyMaster' could not be found. I've got it working by using FindControl() instead of a property on the MyMaster page, but IDs in the master page could change.

+3  A: 

I've tended to do the following with Web Site projects:

In App_Code create the the following:

BaseMaster.cs

using System.Web.UI;

public class BaseMaster : MasterPage
{
    public string MyString { get; set; }
}

BasePage.cs:

using System;
using System.Web.UI;

public class BasePage : Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        if (null != Master && Master is BaseMaster)
        {
            ((BaseMaster)Master).MyString = "Some value";
        }
    }
}

My Master pages then inherit from BaseMaster:

using System;

public partial class Masters_MyMasterPage : BaseMaster
{
    protected void Page_Load(object sender, EventArgs e)
    {
        if (!string.IsNullOrEmpty(MyString))
        {
            // Do something.
        }
    }
}

And my pages inherit from BasePage:

public partial class _Default : BasePage
Zhaph - Ben Duguid
I'll go try that out.
Iain M Norman
+1  A: 

I found some background to this, it happens because of the way things are built and referenced.

Everything in App_Code compiles into an assembly.

The rest, aspx files, code behind, masterpages etc, compile into another assemlby that references the App_Code one.

Hence the one way street.

And also why Ben's solution works. Thanks Ben.

Tis all clear to me now.

Iain M Norman
Yay for clarity :)
Zhaph - Ben Duguid