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

One RadAjaxManager in master page - issues?

15 Answers 744 Views

Ajax

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

SamVanity asked on 20 Nov 2007, 10:15 AM

Hi,

I am thinking about adding the AjaxManager to the master page instead of one manager for each page.

Is there any disadvantage of using a single RadAjaxManager performance wise? I have a common type for Masterpage so I don't have to use findcontrol.

In the help file,

6) RadAjaxManager and RadAjaxPanel at the same application

There are some known issues when using both the manager and the panel in some complex applications - MasterPage or WebUserControls. However, note that a single RadAjaxManager (and no panels) in the master/main page could handle all the scenarios.

What are the known issues? Since RadAjaxManager cannot ajaxify asp:panel anymore, it is not as easy to use as the RadAjaxPanel. I want to avoid any issues beforehand before I add a RadAjaxManager to my masterpage.

In addition, about RadCodeBlock:

What's the difference between using it and a regular asp:placeholder? If I enclose the <%=%> within a placeholder, it works as well. I need to know the advantage/disadvantage of using either performance wise. Since both are derived from UI.Control and don't have any additional functionalities... And since you don't have any info about it in the help file, I don't really see the point of having this extra control..

15 Answers, 1 is accepted

answered on 21 Nov 2007, 12:06 PM

Hi Sam,

Thank you for these questions.

1)
I am thinking about adding the AjaxManager to the master page instead of one manager for each page.

Is there any disadvantage of using a single RadAjaxManager performance wise? I have a common type for Masterpage so I don't have to use findcontrol.

I believe this is the best approach -- access the AJAX Manager through a property from the MasterPage. No, there are not any disadvantages so feel free to follow this approach.

2)
RadAjaxManager and RadAjaxPanel at the same application
What are the known issues?

There are several scenarios having both panel and manager in the same application, which throw errors and are hard or even impossible to resolve over ASP.NET AJAX base. Therefore, we recommend to use RadAjaxPanel in simple implementations only and leave the manager-only approach for the more complex scenarios.

3)
In addition, about RadCodeBlock:

What's the difference between using it and a regular asp:placeholder?

Very good question! Actually there are no differences for the time present -- you can use either the placeholder or RadCodeBlock. We may however include additional functionality in RadCodeBlock in future, which the placeholder will miss.

4)
RadAjaxManagerProxy1.AjaxSettings.AddAjaxSetting(SomeCtl, SomeCtl)

returns an error while performing ajax postback

RadAjaxManagerProxy has "codeless purpose" -- it should help developers AJAX-enabling their applications design-time only. This is the reason we have not added AjaxRequest events for the proxy for example -- if you need some code, you can get the master manager instance and use it instead.

I hope this information helps.

Regards,
Konstantin Petkov
the Telerik team

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

answered on 30 Apr 2008, 09:41 AM

I had a web app that worked ok with RadControls for ASP.NET Q1 2008.
I am trying to convert to RadControls for ASPNET AJAX Q1 2008.
Before I had RadAjaxManager in the master page. But now, even when I have removed all references to RadAjaxManager in the code, I get the following error. (When I do a global search I find no mention ofRadAjaxManager in the code.) How can I resolve this error?

*************

Server Error in '/' Application.

Only one instance of a RadAjaxManager can be added to the page!

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: Only one instance of a RadAjaxManager can be added to the page!

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


            [InvalidOperationException: Only one instance of a RadAjaxManager can be added to the page!]
   Telerik.Web.UI.RadAjaxControl.OnPageInit(Object sender, EventArgs e) +163
   System.EventHandler.Invoke(Object sender, EventArgs e) +0
   System.Web.UI.Page.OnInitComplete(EventArgs e) +2062312
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +963

Version Information: Microsoft .NET Framework Version:2.0.50727.1434; ASP.NET Version:2.0.50727.1434

answered on 01 May 2008, 02:12 AM

Konstantin Petkov

Although I have not yet determined exactly what was wrong I isolated the problem and now I can continue working on the project.
With 2 particular user controls removed from the project it would run without the error.

Later I will re-build these user controls from scratch and problably the problem will be gone.
If this kind of problem happens to others I recommend deleting all pages or user controls from the project and adding them one by one or in groups until you can isolate the problem.
Because the error message does not provide any indication of where the problem occurred.

John