Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 3 of 3

Thread: Conflict With DotNetNuke

  1. 02-25-2010, 09:59 AM #1
    Hank is offline Member
    Join Date
    Nov 2007
    Posts
    42

    Default Conflict With DotNetNuke

    I have had ML8.0 running for some time in a subdirectory (website.com/d).

    However I just installed DotNetNuke (the regular version, notASPDNSF) in the root, and now when I go to my aspdnsf installation in the "d" subdirectory I get this error message:

    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 '/d/App_Code/HTML/' does not exist.

    Source Error:

    Line 110: -->
    Line 111: <codeSubDirectories>
    Line 112: <add directoryName="HTML" />
    Line 113: </codeSubDirectories>
    Line 114: </compilation>

    Any idea how to correct this?
  2. 02-25-2010, 11:44 AM #2
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    Sounds like a .NET web.config inheritance issue. There are a few ways around this is you do a little looking around online. This article might be a good place to start as the example he gives is actually using DNN.
    ECommerce Shopping Cart
  3. 02-25-2010, 03:02 PM #3
    Hank is offline Member
    Join Date
    Nov 2007
    Posts
    42

    Default

    If anyone comes across this again I found a solution here:

    http://www.cynotwhynot.com/blog/post...plication.aspx

    You were right, it is an inheritance issue when DotNetNuke is in the root and another .NET application is in a subdirectory.