RadAjaxManager in User Controls

3 posts, 0 answers
  1. Patrick Rills
    Patrick Rills avatar
    5 posts
    Member since:
    Jan 2010

    Posted 25 Jan 2012 Link to this post

    I have a page that has several user controls in it.  The page inherits from a master page, and that master page has a single RadAjaxManager control on it.  Every user control has a RadAjaxManagerProxy that handles ajaxing just the child controls contained inside that user control.  Everything is functional, but there is some behavior I didn't expect.

    For example, like I said above, User Control 1 has it's own RadAjaxManagerProxy on it that ajaxifies a RadButton to a RadGrid.  When the button is clicked in User Control 1, the RadGrid is updated as expected; however, User Control 2 is also updated (another user control on the same page with it's own RadAjaxManagerProxy).  Is that behavior expected?  I thought if a button was ajaxified, only the controls specified would be updated when an ajax request was initiated?  So why is User Control 2 updated as well?  Am I misunderstanding the functionality? 
  2. Iana Tsolova
    Admin
    Iana Tsolova avatar
    3388 posts

    Posted 29 Jan 2012 Link to this post

    Hello Patrick,

    The described behavior is not expected and it worths further investigation. Are the user controls loaded dynamically? Can you share sample code which illustrates the case?

    Greetings,
    Iana Tsolova
    the Telerik team
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now
  3. Patrick Rills
    Patrick Rills avatar
    5 posts
    Member since:
    Jan 2010

    Posted 04 Feb 2012 Link to this post

    I was unable to recreate the behavior in a separate web application so it must be some bad code I had somewhere else in the page that caused the ajax to "disconnect"

    What ultimately fixed it in the web project where I was having the problem, was moving a call to a method that iterated through every control on the page from Page_Init to Page_Load.  Not sure why that fixed it but it did.
Back to Top