I have been given the task of upgrading our portal to the latest DNN. Everything has gone smoothly as far as DNN itself. I am also replacing some of our custom controls with Ajax.NET and AjaxToolKit. The toolkitcontrols seem to work somewhat, but the Ajax portions of the stuff DO NOT. I have seen other posts about adding the script manager to the skin (I have done this) and also changing the container to have an updatepanel (also have done this). I have 2 problems.

1. The Ajax stuff does not seem to work, postbacks are issued instead of partial updates. (the same code works fine outside of DNN)
2. The Tabs in the tab container in IE appear to only have half a tab (works fine in FF and Safari)

If anyone has an ideas I would love to hear them.

Vladan - you can add a script manager to a control but you have to be extra careful that you only have one control that has the script manager and that it appears before the modules that will use it - personally I put the script manager in the default.aspx that way there is no way to get something "under" it and I know its available on any tab i create

but the skin would work too

 

---

Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules

Hmm.... I know that you can add it to the page itself, or to the skin... but if you think of modules as products, you often see that you don't have access changes to Default.aspx (which is ok by me), and killing the independence of skins by counting that a skin must have a ScriptManager to work correctly sounds scary to me... I even don't like the web.config changes, but they are the least intrusive and easily done by everyone.

 

---

Thanks,
Vladan Strigo
NETMedia

My website: Vladan.Strigo.NET

Vladan.Strigo.NET: Projects
* Advanced VS2005 development approach - BlankModule
* DNN & Microsoft Ajax best practices guidance

Vladan.Strigo.NET: Resources
* Comprehensive list of DNN 4 Module development resources