dreggin,

Move the <location path ...> up one section just above <system.webServer>
Close after </system.web> just as before.

I have just tested this and it works fine with most DNN modules installed.  I created a page with the Links, Wiki and form & List modules loaded on the same page.

Unless I am not understanding what you are doing I believe that everything is working fine now.  Let me know how you make out. 

DNN0501
    Website                           (root application)
         ScrewTurnWiki           (application under root)


DNN Version: 05.01.00 (773)
Platform:        VISTA Business

<location path="." inheritInChildApplications="false">
  <system.webServer>
      <modules>
        ...
  </system.web>
</location>


mikez

RegGFX,

Short answer: The web.config files for DNN 4.8.2 & DNN4.9.4 are formatted differently than DNN5.01.  This may be part of the problem.  See below for more details.

My original search was for a solution for running DNN on the same server as SharePoint (WSS 3.0).  I did not do any full testing for DNN other than the latest version of 5.x.  The test I did using DNN 05.01.00 (773) was to see what was different using DNN in the root instead of SharePoint.

I took a fast look at the web.config files for:
DNN 4.8.2
DNN 4.9.4
DNN 5.01.00

The <system.webServer> section for DNN4.8.2 & DNN4.9.4 is at the end of the web.config file.
The <system.webServer> section for DNN5.x is before the <system.web> section.

The test under DNN5.1 shows that both sections need to be included between the <location> tag.


Suggest that you use the DNN5.1 web.config as a "guide" for DNN4.x.


Obvious question: Did you enable Ajax in the Host settings under DNN 4.9.4?


mikez
 

Yes, I am noticing the exact same thing... even with the suggestions(which were helpful in trouble shooting) I too am still finding the any of my true ajax modules plus 3rd party Ajax modules STILL break if you try to run a DotNet child application on any DNN version on or after 4.8.2. The child app will work but all the modules stop rendering and give me a script error on any DNN version greater that 4.8.2. I wish i knew exactly what changed and why

Its almost like being stuck in the year 1955 or DNN version 4.8.2. When a work around is found it'll be like going "Back to the Future"
Very thankful to everyone's input on this. Still searching for a solution that will allow us to use DNN 4.9.x along with a DotNet child application where the inherit child application tag won't break our AJAX modules or stop them from running.