Today for the first time I had the occasion to use the DotNetNuke.Framework.AJAX.WrapUpdatePanelControl in a module control that had just one section that would benefit nicely from AJAX. As I had seen an example somewhere showing this new (DNN 4.5.2) method called in a module control's Load event handler, that's where I put it (along with the usual call to AJAX.RegisterScriptManager).

I then found that I was having problems with a checkbox that would remain checked visually but which was loosing track of its Checked property in code and a DropDownList control not retaining its viewstate and hence not firing its SelectedIndexChanged event. Both these controls initially had their visibility set to false in the .ascx and were being revealed in response to asynch postbacks. Knowing that dynamically loaded controls should usually be created as early as possible in the page life cycle, I then moved the creation of the UpdatePanel into the Init event handler. All began working as it should.

Tip for the day - call WrapUpdatePanelControl in the Init not Load event handler:

Protected Sub ListEditor_Init(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Init
        If DotNetNuke.Framework.AJAX.IsInstalled Then
            DotNetNuke.Framework.AJAX.RegisterScriptManager()
            DotNetNuke.Framework.AJAX.WrapUpdatePanelControl(Me.pnlUpdate, True)
        End If
End Sub

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

I'm was quite certain that you would need to call AJAX.WrapUpdatePanelControl on both initial load and all postbacks as well which makes sense knowing that any dynamically created controls must be re-created (but not re-populated or re-databound) each cycle. 

To test this, I just created a test module which wrapped a panel containing an auto-postback dropdownlist and a textbox with a dynamically created UpdatePanel on each and every load event. Each time I selected an item in the dropdownlist it's value appeared in the textbox as designed without a full postback.

I then moved calling AJAX.WrapUpdatePanelControl into an Not IsPostback block so that it would be called only on the first load. The first time an item was selected in the dropdownlist it appeared in the textbox with an asynch postback without a complete rendering of the page. The second and subsequent selections from the dropdownlist still displayed the selected value in the textbox but did so with a full postback and complete rendering of the page.

So much to learn about this AJAX "stuff" and so little information/tutorials available beyond the basics!

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Michael,

I see that you have it in the Page_Load and have no issues.  That is where I typically put mine as well, however, I guess I always did it under if(!isPostBack) so that it only did it once, and all of my examples work......am I possibly running a risk of it not working?

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services