Hi there,

Could someone pease point us in the right direction regarding whether DNN should be installed in a virtual directory, or straight under the default web site. We currently have a website e.g.  www.domain.com which has many virtual directories under it, including custom applications, OWA etc. We would like to have www.domain.com/Default.aspx to go to DNN. Unfortunately, when we tried to install DNN at the default website root (luckily in the test environment), it broke the  underlying applications including OWA. This is because of the httphandlers dnn uses and the fact that ASP.NET does not allow one to clear the httphandlers for a sub-directory, once they are set at the default website. There are many threads about that.

DNN runs well as a virtual directory, does not break other applications, but the setback is that the website URLs will be http://www.domain.com/Dotnetnuke/Defa... . This is not ideal. Sure, we can put a default.htm or whatever in the default website root which redirects to the virtual directory http://www.domain.com/Dotnetnuke/Defa..., but that seems ungraceful.

Is there any way of either installing DNN in a virtual directory, but making it accessible using a root url like www.domain.com/Default.aspx, while not breaking other virtual directories like www.domain.com/owa/Default.aspx and www.domain.com/CustomApp/Default.aspx?

We are running DNN 05.04.02 (66) on Windows Server 2008 R2, IIS 7, is a DC and has Exchange and SQL.

Thank you in advance!

I just got one more question since DNN 5.4.x is running .net framework 3.5 and virtual web app is built using .net framework 2.0. How do you stop child inheritance for sectiongroup ?

Jeff, Thank you for you reply - It will be nice if I can run as a second site, but that is not option for me in this case. When I setup DNN 5.4 using framework 3.5 but virtual web app using framework 2.0 will generate the following error: 
---
Parser Error Message: Section or group name 'system.web.extensions' is already defined. Updates to this may only occur at the configuration level where it is defined.

Source Error:

Line 3: Line 4: Line 5: Line 6: Line 7:

Source File: C:\VirtualWebApps\IQC\web.config    Line: 5 

Section or group name 'scripting' is already defined. Updates to this may only occur at the configuration level where it is defined. (C:\VirtualWebApps\IQC\web.config line 6)

Section or group name 'scriptResourceHandler' is already defined. Updates to this may only occur at the configuration level where it is defined. (C:\VirtualWebApps\IQC\web.config line 7)

Section or group name 'webServices' is already defined. Updates to this may only occur at the configuration level where it is defined. (C:\VirtualWebApps\IQC\web.config line 8)

Section or group name 'jsonSerialization' is already defined. Updates to this may only occur at the configuration level where it is defined. (C:\VirtualWebApps\IQC\web.config line 9)

Section or group name 'profileService' is already defined. Updates to this may only occur at the configuration level where it is defined. (C:\VirtualWebApps\IQC\web.config line 10)
Section or group name 'authenticationService' is already defined. Updates to this may only occur at the configuration level where it is defined. (C:\VirtualWebApps\IQC\web.config line 11)

-----------------------

 If I can upgrade my application to 3.5 framework then the error will go away but again that's not an option also. Seems to me the error generate due the inheritInChildApplications start at <system.web> and not at <configSection>

Any help is greatly appreciated.
dinh