R – Stack overflow when setting MasterPage properties

asp.netmaster-pagesnetuser-controls

I'm getting a stack overflow when tryin to set a public property in a MasterPage from an ASPX page.

I'm making a "greeting card" editor, using a TabContainer. Each tab has a user control, and everything is updated when active tab is changed – while doing so I need to store all the data away in master page properties.

From the ASPX page:

protected void tcTabs_ActiveTabChanged(object sender, EventArgs e)
{
    Master.Message = "blahblah";
}

From the MasterPage:

public string Message
{
    get { return Message; }
    set { Message = value; }
}

And this is where I get a stack overflow; in the set {}. Doesn't really matter what I try to set, I get the same problem every time. I'm sure I'm missing some minor thing, but as far as I can see I'm following all the examples I've found.

Best Answer

The problem is that the Message property is calling itself. You need to set a member variable or control property.

Edit: example:

string mMessage = string.Empty;

public string Message
{
    get { return mMessage; }
    set { mMessage = value; }
}

Related Solutions

C# – How and when to use ‘async’ and ‘await’

When using async and await the compiler generates a state machine in the background.

Here's an example on which I hope I can explain some of the high-level details that are going on:

public async Task MyMethodAsync()
{
    Task<int> longRunningTask = LongRunningOperationAsync();
    // independent work which doesn't need the result of LongRunningOperationAsync can be done here

    //and now we call await on the task 
    int result = await longRunningTask;
    //use the result 
    Console.WriteLine(result);
}

public async Task<int> LongRunningOperationAsync() // assume we return an int from this long running operation 
{
    await Task.Delay(1000); // 1 second delay
    return 1;
}

OK, so what happens here:

Task<int> longRunningTask = LongRunningOperationAsync(); starts executing LongRunningOperation
Independent work is done on let's assume the Main Thread (Thread ID = 1) then await longRunningTask is reached.

Now, if the longRunningTask hasn't finished and it is still running, MyMethodAsync() will return to its calling method, thus the main thread doesn't get blocked. When the longRunningTask is done then a thread from the ThreadPool (can be any thread) will return to MyMethodAsync() in its previous context and continue execution (in this case printing the result to the console).

A second case would be that the longRunningTask has already finished its execution and the result is available. When reaching the await longRunningTask we already have the result so the code will continue executing on the very same thread. (in this case printing result to console). Of course this is not the case for the above example, where there's a Task.Delay(1000) involved.

Best Answer

Related Solutions

C# – How and when to use ‘async’ and ‘await’

Related Topic