Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Creating a Virtual Directory with DNN within an ASP.NET websiteCreating a Virtual Directory with DNN within an ASP.NET website
Previous
 
Next
New Post
3/30/2008 7:37 PM
 
Bob Zagars

Joined: 2/8/2007
Posts: 14

I created DNN v4.8.2 as a Website on Server 2003 IIS and it worked correctly but I can not seen to make it a Virtual Directory within another ASP.NET website.  Can someone inform me or direct me to documentation on how to setup a Virtual Directory installation?
 
New Post
3/31/2008 9:08 AM
 
Jeff Cochran


Joined: 6/3/2005
Posts: 2799

What happens ?  Errors?

Jeff
 
New Post
4/3/2008 9:11 AM
 
Bob Zagars

Joined: 2/8/2007
Posts: 14

Thanks for responding.  I will have to get back to you on the exact error.  I reinstalled my server software because I felt I had too many betas on it.  I can tell you I can run DotNetNuke on my local development box as http://localhost and it works fine.  I had read that all I had to do was reference the portal and presto my system is running.  I did setup a location as a virtual directory within my web site to run DotNetNuke http://www.zagarsandevans.com/DotNetNuke which after I got it running on localhost I copied the whole system onto the server and put a reference in the database to the same portal.  What I read was I could reference within the database www.zagarsandevans/DotNetNuke and I would be up and running.  I also put a reference to the location without www on the string.  I have received my books I ordered and most of my other tools for developing modules which it is just a matter of getting this to show on a production box.  If you can give me some insight to save time, please do.
 
New Post
4/3/2008 9:39 AM
 
Jon Seeley

www.seeleyware.com
Joined: 8/8/2006
Posts: 597

What it comes down to is the web.config inheritance.  When you set up a virtual directory within an existing ASP.NET application then settings from the web.config in the first application roll-down or are inherited by the second application.  To fix this, the web.config in the virtual directory need to have some <clear /> tags added in all the appropriate sections such as <connectionstrings> <httphandlers> <appsettings> and several more that I can't remember off the top of my head.  It is typically "easier" (especially with DNN, since every time you update you'll have to remember to add those <clear /> tags again) to just have it as a separate website altogether.

The above only applies if the base application (website) has settings the web.config that would conflict with the settings in DNN -- in other words, if you have a website in IIS that does not have a web.config or does have one but it is virtually empty, you don't need to worry about this.  I have 5-6 instances of DNN on my development server and several of them are set up as virtual directories (some where they are subs of another ASP.NET app, others that are merely subs in general)

-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
4/3/2008 12:48 PM
 
Bob Zagars

Joined: 2/8/2007
Posts: 14

Thank you for responding.  I have also setup a clean installation which is behind no other ASP.NET website.  It is located at http://zagarsdevelopment.net the error I am getting is a parser error.  You can see the error remotely and basically the description is as follows.

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'DotNetNuke.Common.Global'.
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Creating a Virtual Directory with DNN within an ASP.NET websiteCreating a Virtual Directory with DNN within an ASP.NET website


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