I have a new 4.7 DNN installation and am attempting to migrate an old site to DNN (I'm a DNN newbie). The old site is .Net 1.1 and it has several virtual directories with .Net 2.0 applications (different application pool). When I try to create similar virtual directories under the DNN web site the applications stop working - errors relating to the inherited root dnn web.config settings.

I've read a bunch of threads about similar issues and was wondering if anyone has come across a solution - not a DNN issue, but maybe someone here has had this or similar issues and figured out a work-around.

Thanks in advance,

-Lee

Lee -

I have several virtual directories running under DNN. I had to make sure things were cleared in the child web.configs manually as Mike suggested:

    <httpModules>
     <remove name="UrlRewrite" />
     <remove name="Exception" />
     <remove name="UsersOnline" />
     <remove name="DNNMembership" />
     <remove name="Personalization" />
     <remove name="Compression" />
     <remove name="RequestFilter" />
    </httpModules>

I also had to copy some dlls from the DNN bin dir into each child app bin directory. I found that the easiest way to do all of this is to set:

<customErrors mode="Off"/>

So that you can catch everything. Youo should be able to work out which dll needs copying to the child bin directory from the errors.

Post back here with any errors you get that you can't work out.