In my haste... i accidently posted this to the "Chat about it" forum when i should have posted this here... please forgive me DNN forum.

Anyway... here is my issue
We have just completed a fresh (CLEAN) install of DNN 4.9.0 with no problems.
As we near completion of the site, we've noticed that AJAX is not being loaded into the DNN Site!... We even checked the settings to make sure that AJAX was enabled. And still NO AJAX DRIVEN MODULES WORK whan we add them to the content page.
The Server ASP.NET 2.0 AJAX EXTENSIONS 1.0 are loaded on the server where our DNN 4.9.0 resides.

Is there anything we can check or do to fix this problem? Any work arounds without starting completely over?
Please Advise ASAP

Thanks

Well after further review, We believe we have found the problem... It has to do with trying to run a child DotNet application as a sub application under DotNetNuke in IIS. This problem is only apparant in DNN versions after 4.7+

We run a sub Dot Net application as a Child DotNet application under DotNetNuke in previous versions such as DNN 4.7 by adding a line of code that said <location inheritInChildApplications="false"> before the <system.web> tags and then placing a </location> at the next line after </system.web>

THIS allowed us to successfully run sub DotNet applications under DotNetNuke in IIS... HOWEVER, a problem occured when WE UPGRADED TO ANYTHING PAST 4.7.
It appears that if you use <location inheritInChildApplications="false"> in DNN 4.8+ or DNN 4.9.0 this BREAKS the AJAX Script Manager to the point where you get an AJAX Script Manager error and thus does not LOAD AJAX.

Well that was the problem... and we verified that this is the case with any DNN version after 4.7+.

Now we have to find a solution or submit a "BUG" report to the DNN core team to help us find a solution to permit us to run child DotNet applicaitons under DNN 4.8+ and DNN 4.9+ without getting a AJAX script manager error.

Is there anyone out there who is running a sub DotNet application under DNN in IIS while using DNN 4.8+ or DNN 4.9+

Yes we were thinking the same thing of running this as an IFRAME but unfortunatally our DotNet Application which did work in version 4.7 and under as a child or separate application in IIS, has to function as a child or sub DotNet application.

What we are trying to find out is, What was changed in versions 4.8+ to 4.9+ which kills our ability to run a DotNet sub without destroying the Ajax Script Manager.

This did work very well in DNN 4.7 but not in 4.8+ to 4.9+ very interesting indeed.