When you have a simple UpdatePanel with a Trigger and UpdateProgress where AssociatedUpdatePanelID is specified, the UpdateProgress template does not appear at all. I am using Beta 2. Here is a simplified version:

<form id="form1" runat="server">
 <div>
 <asp:ScriptManager ID="ScriptManager1" runat="server"></asp:ScriptManager>
 <asp:UpdatePanel ID="UpdatePanel1" UpdateMode="Conditional" runat="server">
  <ContentTemplate>
   <asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
  </ContentTemplate>
  <Triggers>
   <asp:AsyncPostBackTrigger ControlID="Button1" />
  </Triggers>
 </asp:UpdatePanel>
 <asp:UpdateProgress ID="UpdateProgress1" AssociatedUpdatePanelID="UpdatePanel1" DisplayAfter="0" runat="server" DynamicLayout="false">
  <ProgressTemplate>
   Loading...
  </ProgressTemplate>
 </asp:UpdateProgress>
 <asp:Button ID="Button1" runat="server" Text="Button" OnClick="Button1_Click" />
 </div>
</form>

The CodeBehind is simply:

protected void Button1_Click(object sender, EventArgs e)
{
	System.Threading.Thread.Sleep(1000);
	TextBox1.Text = DateTime.Now.ToString();
}

UpdateProgress can display well when using AssociatedUpdatePanelID and Triggers,and you need to attach some javascript to add InitializeRequest and EndRequest.Here is a useful link with sample codes for your reference.
http://ajax.asp.net/docs/ViewSample.aspx?sref=UpdateProgressOverview2

Thanks for the response.

I would consider your example a workaround to the bug. In my example in the original post, clearly the UpdateProgress in associated to the UpdatePanel. Anything that causes the updatepanel to do an AsyncPostback should cause the UpdateProgress associated with it to display.

My real page has 4 UpdatePanels, so now I will have to match each AsyncTrigger to each one of my 4 UpdateProgress (I wanted 4 seperate UpdateProgress on purpose).

Hope this gets addressed in a future version.

Thanks,
Perry

Hello

Will this be fixed in RTM version?
As this is still a problem in RC...

 Mindaugas

There are 2 conditions here that i've discovered:

1 - The button is located in the UpdatePanel control
In this condition, the UpdateProgress is triggered and is displayed irrespective of whether the AssociatedUpdatePanelID is set on the UpdateProgress.

 
2 - The button is located OUTSIDE the UpdatePanel control
In this condition, if the AssociatedUpdatePanelID is set on the UpdateProgress control, then the control is NOT displayed during async postback. However if you don't set the AssociatedUpdatePanelID, then the UpdateProgress IS displayed (presumably because it is associated  at a page level).

 

 This reeks like a bug to me. Irrespective of whether the button is located inside or outside of the UpdatePanel, I've got the trigger on the panel set to fire an async postback when the button is clicked. Therefore when the button is clicked, the updatepanel will refresh and that should notify the progress (especially if AssociatedUpdatePanelID is set).

 I can provide a repro of this, or explain further if necessary.

 
Thanks,
 
-X
 

Hi Mindaugas,
    ASP.NET AJAX RTM will be released a little later than this month according to the plan - but not far off now. Wish all of these issues will be resolved in Ajax RTM. Let's pay attention to Ajax updates from this website - http://Ajax.asp.net.

This bug is still present in the RTM release

Has this been fixed yet?

I'm not sure you can necessarily call this bug, although the documentation on expected behaviour, as with all the AJAX base and toolkits controls is scant.

However as long as you ensure the control raising the event is in an update panel, and include your updateprogress control in the same panel (with it's AssocUpdatePanelID set to this panel) you shouldn't find any problems. You can use this technique to have multiple progress controls associated to different initiating controls in one page.

I am accepting this as behaviour by design rather than a bug unless I hear to the contrary from MS.

Here is the documentation on the UpdateProgress.  Its at http://ajax.asp.net/docs/overview/UpdateProgressOverview.aspx

You associate an UpdateProgress control with an UpdatePanel control by setting the AssociatedUpdatePanelID property of the UpdateProgress control. When a postback event originates from an UpdatePanel control, any associated UpdateProgress controls are displayed.

I would consider the current implementation a bug.  The UpdateProgress is not performing as the documentation states.  This is very frustrating because the control simply does not perform as it is documented.

Wally 

I'm a noob at ajax.net, but if you are having problems, what worked for me is putting the triggering control (like a dropdown) within an UpdatePanel, and then pointing the appropriate Progress indicator to that panel (via AssociatedUpdatePanelID).  Don't point the Progress control to the UpdatePanel containing the new content.

for large update panels with more than one control, you are screwed though.

it really seems to me the indicator should be set to the panel whose content is being updated, not the source of the postback event.
 

 

 

 

 

 

 

For me it also seem like a bug, since it doesn't behave as stated in documentation as well is it should behave in my opinion.

And.. it wasn't fixed in the final version of AJAX 1.0

Not sure how anyone can suggest this isn't a bug.  Basically you can't have your action button (for example) outside of your updatepanel and have an update progress. 

The nice side affect of not using AssociatedUpdatePanelId is that if you have other update panels on the page then they will also trigger this updateprogress as well as their own.

Great......

Is there any solutions for this problem? I've had action button outside the updatepanel also and updateprogress doesn't show anyway - only if move action button inside updatepanel:(.

Hi all,

I was also looking for a solution. And I found it!!!

Refer to this article at CodeProject - http://www.codeproject.com/KB/ajax/UpdateProgress.aspx

Basically, all u need to do is just to add in some javascript. Remember to update the javascript to your control ID.

All the best.