ASP.NET dynamically created controls and Postback

Solution 1:

For anyone else trying to do something like this: don't. Instead, think of the flow of information and understand that there is a better way to do it. The input control(s) do not need to be dynamically created. They can be static, and upon filling out and submitting on one, that information has to go somewhere (database, cache, session, for example). Once its there, on postback, loop through all items in your storage of choice and create a display for them.

That is what I've done and it has made life a lot easier. Hope it helps someone.

Solution 2:

void lbAddFilter_Click(object sender, EventArgs e)
{
    TextBox tb = new TextBox();
    tb.ID = "tb" + DateTime.Now.ToBinary().ToString();
    pnlFilter.Controls.Add(tb);
}

That's not going to work - it's a lifecycle issue as you inferred in your question. There are lots of ways you can work with this, but Honus Wagner's suggestion is the most flexible.

What's happening here is that you're calling Controls.Add in the event handler and the control is being added to the control list, and on the next request (be it a partial postback, full postback, or new page hit), that control is gone because you haven't persisted it anywhere.

Here's what's happening in your page event lifecycle right now:

1. Page calls OnInit and adds your LinkButton
2. The user clicks the LinkButton
3. Page calls OnInit to begin the postback request. The LinkButton is recreated
4. The event handler is called, which dynamically creates your TextBox and adds it to the control collection
5. The user clicks the LinkButton again
6. Page calls OnInit to add the LinkButton again. The pnlFilter.Controls collection is empty at this point, except for any elements you've declared statically in your markup.
7. Event handler is called and a new TextBox is added to the control list.

I'm not sure that it's the best practice, but I've had success with a model similar to this (note that I haven't tested this code - it may need adjustment):

protected override void OnInit(EventArgs e)
{
    base.OnInit(e);

    LinkButton lb = new LinkButton();
    lb.ID = "lbAddFilter";
    pnlFilter.Controls.Add(lb);
    lb.Text = "Add Filter";
    lb.Click += new EventHandler(lbAddFilter_Click);

    // regenerate dynamically created controls
    foreach ( var control in PersistedControls )
    {
        pnlFilter.Controls.Add(GenerateControl(control));
    }
}

private IList<Control> _persistedControls;
private const string PersistedControlsSessionKey = "thispage_persistedcontrols";
private IList<Control> PersistedControls
{
    if (_persistedControls == null)
    {
        if (Session[PersistedControlsSessionKey] == null)
            Session[PersistedControlsSessionKey] = new List<Control>();
        _persistedControls = Session[PersistedControlsSessionKey] as IList<Control>;
    }
    return _persistedControls;
}    

void lbAddFilter_Click(object sender, EventArgs e)
{
    TextBox tb = new TextBox();
    tb.ID = "tb" + DateTime.Now.ToBinary().ToString();
    PersistedControls.Add(tb);
    pnlFilter.Controls.Add(tb);
}

Note that I'm not sure about adding actual Control objects to the Session store - I believe there are issues with the control IDs that will cause errors on postback (maybe a Control isn't serializable?). In the solution I developed, I generated a fresh TextBox/Label/ComboBox/etc in my equivalent of the GenerateControl method, and stored a custom container class in the PersistedControls collection that contained the various properties of the UI control that I would need to generate it on each page Init.

Solution 3:

I believe that you'll need to recreate each control on every postback.

I know that the Repeater control stores enough information about its children to recreate them when databound... You may be able to use it to save a little work.