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 conflicting with other DotNetNuke virtual drectoryDNN conflicting with other DotNetNuke virtual drectory
Previous
 
Next
New Post
4/2/2009 5:31 AM
 

Hi there

Prior installing DNN 5, I have .Net 2 application called: CaseManagemet and after installing DNN 5 on the root level. Suddenly the CaseManagement application is stop and it seems it's trying to access the DNN web.config. Here's the sample URL that I need to try to access to: http://www.xxx.com/CaseManagement

Any ideas?

Here's the error below. I can setup the CaseManagement put as sub domain BUT that's not what we want due to the SSL certificate that we have. 

 

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

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

Source Error:

Line 127:      -->
Line 128:      <codeSubDirectories>
Line 129:        <add directoryName="HTML"  /> Line 130:      </codeSubDirectories>
Line 131:    </compilation>

 

 

 
New Post
4/3/2009 9:42 AM
 

do not nest applications, especially not physical folders!


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/3/2009 9:13 PM
 

Actually ... I found the solution.

You still be able nested the application by putting

Never mind .. I worked out myself.

On the root level of the web.config, you have to put this on your web.config

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

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN conflicting with other DotNetNuke virtual drectoryDNN conflicting with other DotNetNuke virtual drectory


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