Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...dnn and other web pagesdnn and other web pages
Previous
 
Next
New Post
6/11/2008 10:31 AM
 

what you are trying to do is ensure that an application in aq virtual does not inherit from the root folder, so the answer is "it depends", let me sketch 2 scenarios:

1. Say you have a root IIS web site with a url of www.mysite.com that contains dotnetnuke, and a virtual folder called "someapp" that contains another asp.net site. The dotnetnuke site will work as expected, but the "someapp" virtual will fail as it inherits the dotnetnuke sites settings. To fix this you need to insert the <c/ear/> instructions in the "someapp" web.config

2. Say you have a root IIS web site with a url of www.mysite.com that contains a normal asp.net application, and a virtual folder called "someapp" that contains dotnetnuke. The normal asp.net site will work as expected, and there is a chance that the dotnetnuke site will also work as long as the normal asp.net site does not contain any httpmodules or httphandlers in it's web.config. If it does, then the dotnetnuke site will inherit these settings and may cause dotnetnuke to not work as expected. To fix this you will have to <clear/> the settings in the dotnetnuke web.config BUT ALSO ensure that the existing ones apply i.e.

<httpModules>
      <add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / >

....other definitions

</httpModules>

to

<httpModules>

<clear />
      <add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / >

....other definitions

</httpModules>

 


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
6/11/2008 3:47 PM
 

OK, I have removed the virtual directory I created.

here is the modules setion of my web config file.

<httpModules>
      <!-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->
      <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=xxxxxx" />
      <add name="Compression" type="DotNetNuke.HttpModules.Compression.CompressionModule, DotNetNuke.HttpModules" />
      <add name="RequestFilter" type="DotNetNuke.HttpModules.RequestFilter.RequestFilterModule, DotNetNuke.HttpModules" />
      <add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules" />
      <add name="Exception" type="DotNetNuke.HttpModules.Exceptions.ExceptionModule, DotNetNuke.HttpModules" />
      <add name="UsersOnline" type="DotNetNuke.HttpModules.UsersOnline.UsersOnlineModule, DotNetNuke.HttpModules" />
      <add name="DNNMembership" type="DotNetNuke.HttpModules.Membership.MembershipModule, DotNetNuke.HttpModules" />
      <add name="Personalization" type="DotNetNuke.HttpModules.Personalization.PersonalizationModule, DotNetNuke.HttpModules" />
   </httpModules>

if I add the <clear/> to it I get the following error

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

 
New Post
6/11/2008 4:01 PM
 

Please follow the error messages recommendation and enable RemoteOnly (or else On), and you'll see what the actual error is.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
6/11/2008 4:21 PM
 

this is crazy...all I'm trying to do is run a few asp.net applications on the same IIS server as dnn.

Parser Error Message: The code subdirectory '/eCatalog/App_Code/HTML/' does not exist.

Source Error:

Line 111:      -->
Line 112:      <codeSubDirectories>
Line 113:        <add directoryName="HTML" />
Line 114:        <add directoryName="IFrame" />
Line 115:        <add directoryName="Survey" />

 

App_Code/HTML is part of dnn not my app. why is it looking for that directory?   in my other apps web.config file (not dnn's) I added the <clear/> to the modules and this is what I get.

 
New Post
6/11/2008 6:51 PM
 

you'll have to create empty folders in your vitual directory application for those folders (see http://www.velocityreviews.com/forums/t496755-ltclear-gt-ltremovegt-in-codesubdirectories.html for why)

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...dnn and other web pagesdnn and other web pages


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out