We have a problem with RadAjaxManagerProxy with user controls. We changed the physical ASPX pages into ASCX controls and we load them from a single Default.aspx page. We use RadGrid together with RadComboBox controls to implement filtering and data loading into the grid.
When the pages containing the grid were hosted in a single ASPX page, they worked ok.
When the pages were converted into ASCX controls, we had to put a RadAjaxManagerProxy in them to refer to the master RadAjaxManager inside the master page. However,
we have issues when the controls are interacted with.
One concrete example of the error we face is this one:
- We have a User Control (First.ascx) with a RadGrid and a second ASCX nested inside. Both controls are set as updated by a RadAjaxManagerProxy.
- This second ASCX control (Filter.ascx) has a RadComboBox and the control class exposes a public property to let the parent control get its filtered value. This control also has a RadAjaxManagerProxy, updating the combo boxes.
- A Default.aspx page loads the first control and displays it OK (the grid and the nested user control). When we change the combo box value (this is inside the second user control), the loading panel is displayed (as expected) but it never ends. The server-side event for the RadComboBox is correctly processed and ends but the loading panel still shows the loading animation.
- When the First.ascx was First.aspx (with the same markup and codebehind), the Filter.ascx behave correctly. The error began when we changed it into ASCX.
The other error we face is when we export a RadGrid contents as an Excel file with ExportToExcel method, the method executes but no result is shown to the browser. When the ASCX control having the grid with RadAjaxManagerProxy was a standalone ASPX page with RadAjaxManager, the export was done well.
It seems that somehow the RadAjaxManager doesn't get notified when the postback ends.