This is a migrated thread and some comments may be shown as answers.

[Solved] ResolveUpdateControls not firing

7 Answers 237 Views

Ajax

This is a migrated thread and some comments may be shown as answers.

MMagnumPI9 asked on 05 Jul 2007, 09:06 PM

I cannot get the ResolveUpdateControls to fire for the ajax manager. This exact procedure works in latest asp.net release, am I missing something with the new version?

<asp:ScriptManager ID="ScriptManager1" runat="server" /> 

<telerik:RadAjaxManager ID="AdminAjaxManager" runat="server" 

OnAjaxRequest="AdminAjaxManager_AjaxRequest" 

OnResolveUpdatedControls="AdminAjaxManager_ResolveUpdatedControls">  

                <AjaxSettings> 

                    <telerik:AjaxSetting AjaxControlID="Button1"/>  

                </AjaxSettings> 

            </telerik:RadAjaxManager> 

            <asp:Button ID="Button1" runat="server" OnClick="Button1_Click" Text="Button" />      

                    <radT:RadTreeView ID="AdminTreeView" runat="server">  

                    </radT:RadTreeView>

protected void AdminAjaxManager_AjaxRequest(object sender, AjaxRequestEventArgs e)  

{  

}  

protected void AdminAjaxManager_ResolveUpdatedControls(object sender, AjaxUpdatedControlsEventArgs e)  

{  

}  

protected void Button1_Click(object sender, EventArgs e)  

{  

}

7 Answers, 1 is accepted

answered on 06 Dec 2007, 02:01 PM

Hello Pieter,

The AjaxSettingsCreating and AjaxSettingsCreated events are not meant to be replacement for the ResolveUpdatedControls event. Actually let me add some background on it - the ResolveUpdatedControls event was introduced in our ASP.NET RadAjax control to handle cases where the initializing control is wiped out after triggering an update. Due to the mechanism we use for our ajax, such scenario was possible and this was used like a workaround.
The Prometheus Ajax on the other hand is based on MS AJAX and uses UpdatePanels created on the fly, to update the controls. In this case, the initializing control is always on the page as it is surrounded by an UpdatePanel, which the AjaxManager is aware of and thus not throwing any errors that the initiator is missing as it know exactly what happened during the update - which was not the case with the old ajax.

We hope that you understand our position on the matter. If you have encountered a problematic scenario, please describe it here (or even open a support ticket and attach a sample), so we can review it and advise you accordingly.

Best wishes,
Steve
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center