Hello everybody!

I installed DNN3.2.2 in wwwroot folder of IIS (Win2003) and it is working fine. But, I would like to run some other web applications (.NET) which are not part of DNN, so I created the subfolder "MyApps" in wwwroot and placed application folders inside (one application = one subfolder). But when I try to run any of these applications I get a "Confguration error" because DNN's web.config which is in wwwroot is propagated to the subfolders (when I rename DNN's web.config into something else, everything works fine). How can I prevent this propagation? Is there a better way to install DNN in this scenario (other apps on website). I cannot use host headers because I run SSL on the site, and I would like that my first page be www.mycompany.com (and not .../portal or something else).

Thanks in advance!

VD

Nina, I don't think I understand your answer. The problem is in the web.config hierarchy, not bin folder(s). I said - when I rename DNN's web.config into e.g. web2.config, other applications work fine (but DNN doesn't, of course).

In version 3.?? you have to copy the <configSections> from the dotnetnuke web.config to your other projects web.config file.  You also have to copy each of the related files to your bin directory since you have these settings in your other projects web.config.  This is really a pain, but the only way I know around it.  From what I have heard, this is not a problem in the 4.?? version becuase of changes made in the .Net 2.0 framework.

Another option would be to create a seperate web site for DotNetNuke and a seperate site for all your other applications.  To do this you just need to assign a different IP address to each of the web sites (sinceyou are using SSL and cannot use host headers).  You would then have to create the DNS entries to assign the IP addresses to the domain name.

111.111.111.1111: myDNN.site.com
222.222.222.2222: myOther.sites.com