Though that doesn't sound like a bad idea at all, I don't think it's necessary. I have another page with a VERY similar structure and function. It uses almost all the same controls (and in the same way) but manages a different list of data. That page works fine though. It does look a bit strange (font-size and misaligned tab borders) which tells me something outside my code has changed (like implementing the new DOCTYPE.xml files instead of declaring my DOCTYPE locally in the UserControl, or something with my external CSS file. I can't figure out what the difference is functionally between the two pages though. One more reason I suspect I'm trying to do something I shouldn't be with the above code, while it runs under DNN. Keep in mind, the code above runs fine on my DNN site in a standalone .aspx page.

Any of that throw any new flags? The reason I had transitional in the web.config was because of articles like below. You're saying that's improper though, why?

http://vladan.strigo.net/Projects/MSAjaxDotNetNuke4/HowToEnableMSAjaxinDotNetNuke4/tabid/85/Default.aspx

http://drowningintechnicaldebt.com/blogs/dennisbottjer/default.aspx

http://msdn2.microsoft.com/en-us/library/ms228268.aspx

Searching... Reading... Experimenting... SUCCESS!!!!

I'm not 100% sure what the fix was, but here's essentially what I did:

1. Stripped my TabContainer and Tabs
2. Found the page worked!
3. Implemented an Accordion instead of TabContainer
4. Noticed some issues with my update panels and restructured layout to provide more granular control of updates using more update panels
5. Found I couldn't control updates properly and started searching forums
6. Discovered an article that provides the code snippet below (article A)
7. Disabled the "Enable Partial Updates" for the control module
8. Implemented code in (article A) in my page_load event

article A

             If DotNetNuke.Framework.AJAX.IsInstalled Then
                DotNetNuke.Framework.AJAX.RegisterScriptManager()
                Label2.Text = "AJAX Is Installed"
            Else
                Label2.Text = "AJAX Is not installed"
            End If

All said, I think the trouble was a matter of having UpdatePanel's embedded inside Panel's, inside TabContainer in combination with a Master/Content configuration and letting DNN try to manage my ScriptManager.

Hope this thread helps someone else.

Thank you for posting this fix! 

I implemented the following to help my module.  The module actually wraps another control that has the AJAX tab control and no DNN references (the control is totally decoupled from DNN).  I used the following in my module (which does have a tie to DNN) to determine if the script manager installed on the page.

Protected Overrides Sub OnInit(ByVal e As EventArgs)

'AJAX FIX: Must have this to determine if the script manager is available; otherwise the

'ajax controls will not appear. (this happens in production but not in dev.)

If DotNetNuke.Framework.AJAX.IsInstalled Then

DotNetNuke.Framework.AJAX.RegisterScriptManager()

End If

'Does not work; however, may provide

'If AjaxControlToolkit.ScriptControlBase.ScriptManager.GetCurrent(Me.Page) Is Nothing Then

' Me.Controls.Add(New AjaxControlToolkit.ScriptControlBase.ScriptManager())

'End If

MyBase.OnInit(e)

End Sub