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 ...ASP.NET Application in Virtual Directory inside DNN InstallationASP.NET Application in Virtual Directory inside DNN Installation
Previous
 
Next
New Post
11/6/2009 3:43 PM
 

Hey everyone, I have a situation that I need to solve and was hoping some of you might be able to help me out.

I have a DNN 5.1.3 installation as the root of an IIS website. I have another application that I need to be able to access with the same url. for example, my.domain.com is the dnn installation and the VD will be accessible using my.domain.com/vd. Every time I try to access the VD I receive this error.

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 '/biz/App_Code/GP_Advertisements/' does not exist.

Source Error:

Line 164:      -->
Line 165:      <codeSubDirectories>
Line 166:        <add directoryName="GP_Advertisements" />
Line 167: <add directoryName="GP_Awards" /> Line 168: <add directoryName="GP_Bios" />

Source File: D:\Inetpub\myroot\web.config    Line: 166

I found another instance of someone else having the same issue with no resolution. Is there any wayt that I can force the VD application's web.config to not inherit the dnn web.config settings? or even just a way to get it to work. Eventually all of the stuff that is in the VD application will be ported into modules on the DNN site but for the time being we are keeping it separate.

Anyone have any ideas? I'm at a complete loss.

Thanks!

 
New Post
11/7/2009 2:39 PM
 

Kevin

Perhaps a child portal will address your needs?

 

 
New Post
11/9/2009 10:19 AM
 

no a child portal won't do it because it's a completely separate application. I'd like it to run as a Virtual Directory in IIS under the site root. Doesn't seem like I'm going to be able to do it that way. Has anyone else run into this issue?

 
New Post
11/9/2009 11:15 AM
 

Here's how I solved the same problem:

1) Create a subdomain off your main DNN site.  (e.g., mysubdomain.mydomain.com). This creates a folder called "mysubdomain" under the "/subdomains" directory (not under httpdocs where the default DNN got installed).

2) Upload your ASP.NET app files to the subdomain folder (e.g. /subdomains/mysubdomain)

3) Use an IFrame module in your portal to point to http://mysubdomain.mydomain.com

I had originally added <location inheritInChildApplications="false"> to my web.config to prevent a child ASP.NET app from inheriting the parent's web.config, but then the DNN install/upgrade fails.  It took me weeks to track down the issue, so I hope the above solution works for you.  Unless someone else has a better way...

Joan

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...ASP.NET Application in Virtual Directory inside DNN InstallationASP.NET Application in Virtual Directory inside DNN Installation


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