We've never been able to upgrade to the latest versions of DNN 4.9.X because we use a Child DotNet application inside of our DNN Portal.

The issue is we at one time could edit the web.config to prevent child inherit apps from inheriting.
Somewhere between 4.8.2 and greater this ability CEASED to exist.  Now WHY we do not know. 
Therefore we’re stuck in the stone ages of using 4.8.0 because it is a non issue in 4.8.0. But unfortunatelly we cannot upgrade. We saw on the DNN Support site (GEMINI) it was on the road map to be fixed. Does anyone know if this was fixed in version 4.9.x without going to the 5.X versions?

PLEASE ADVISE ASAP.

Does not look like it was fixed in 4.x, nor does it look likely to be fixed.
I would suggest leaping into 5.1.1 when it is made available (but always backup in case you need to leap back).

Alex and Mike thank you for the replies.

I tried using the path attribute on the location tag but received the same result. Which makes sense to me because we are not really dealing with the same issue, and I think that just implies root location.  Yours is one of .net inheritance, which is fixed by that tag.  My issue is that if I fix the inheritance it breaks the dnn ajax functionality, and I need both.

It seems that DNN needs to be able to see the xpath information to see if ajax is installed and so any time a module is loaded that needs ajax it will not be given a script manager.

If anyone has any idea of a workaround it would be greatly appreciated since I utilize a lot of custom and commercial ajax modules.  In the meantime I will hope it is fixed in the first stable release of 5.x.

Thanks