Home/ Questions/Q 8136417
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T10:45:18+00:00

I’m under the impression that a control in a nested UpdatePanel will cause the

  • 0

I’m under the impression that a control in a nested UpdatePanel will cause the top level UpdatePanel to refresh (thus refreshing both UpdatePanels) because any events on that control act as an “implicit” trigger. Is that correct?

I’ve been trying to wire something like this up-

UserControl

   Parent UpdatePanel

   "Show" button

      ASP:Panel

         Dynamically added UserControls, each with UpdatePanels

When the Show button is clicked, the ASP:Panel becomes visible and starts adding UserControls to itself dynamically, based on some back-end logic.

Each of the dynamically added controls (henceforth: UserControls) have their own Atlas-enabled buttons and links, so they have UpdatePanels too. Currently when I click on a link in one of the UserControls, the entire contents of the ASP:Panel disappear, as if it’s being re-rendered. All of my dynamically-added controls disappear, and none of their click events are caught in the debugger.

I’m assuming what’s happening here is that controls that reside in nested update panels are causing the parent UpdatePanel to post back because they’re firing “implicit” triggers. Is there a way for my UserControls to operate autonomously and not mess with the ASP:Panel that contains them?

If not, what strategy should I be pursuing here? If I have to re-render the entire ASP:Panel every time an event happens on one of the (possibly many) UserControls, that means I’ll have to recreate the UserControls, which take a bit of effort to create. I’ll also have to preserve some kind of view state to recreate them. I’m somewhat new to ASP.NET and that sounds intimidating. I’d rather never refresh the top leve UserControl and ASP:Panel if I can avoid it, and let each of the dynamically-added UserControls fire and handle their own events asynchronously.

EDIT: Instead of adding the controls dynamically, I added them to the markup(not a bad solution). So got rid of the controls disappearing problem, because now the controls are not added dynamically but instead exist in the markup. But still the parent UpdatePanel posting is a big performance hit, because all the UserControls are getting posted instead of one. How do I make only one UserControl postback? Also, I would like to know how to get rid of the problem of controls disappearing if added dynamically?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    First off, keep in mind: UpdatePanels do not alter the lifecycle of a page.

    All of the Control Tree (including the UpdatePanels) must be reconstructed just as with a Normal Postback Life-cycle.1 2 The UpdatePanels ensure that only a portion of the rendered (HTML) view is returned. Removing all UpdatePanels should result in the same behavior, except with a full postback. For instance, only the HTML representing a nested UpdatePanel (presumably because data changed) might be sent back in the XHR response.

    To get “true” AJAX consider Page Methods. Alternatively, DevExpress (and perhaps Telerik and others?) offer their own form of “Callback Panels”, which are similar to UpdatePanels, but can bypass parts of the life-cycle (and, as a result often do not support the ViewState model entirely or may introduce their own quirks).

    While not understanding the above is the most likely reason for the controls “disappearing”, here is my rule: Do Not Let [Nested] UpdatePanels Work “Automatically”.

    Edge cases with dynamic controls and nested UpdatePanels will be encountered. There might be a nice way to handle this, but I have failed on multiple different attempts.

    Instead, for every update panel, run with:

    UpdateMode="Conditional"
ChildrenAsTriggers="False"

    With the “Conditional” UpdateMode, make sure to manually specify the Trigger control or call panel.Update() (although this hard-wires the Control) as required. Depending on needs ChildrenAsTriggers="True" might work as well. The big thing is that UpdateMode is not “Always” which is the default.

    After switching to this approach, I have no problem — well, almost none — with nested UpdatePanels.

    Happy coding!

    1 If the page doesn’t render correctly where Partial Rendering (in the ScriptManager) is disabled (e.g. all requests are full postbacks) then there is no reason to expect/believe it will work correctly with UpdatePanels.

    2 There are times when it’s warranted to “cheat” expensive recomputations in the control tree for controls that will not be re-rendered. However, I would consider these advanced cases that should only be done when performance analysis indicates there is a specific need.

    • 0