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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error - allowDefinition=Error - allowDefinition='MachineToApplication'
Previous
 
Next
New Post
8/14/2007 8:46 AM
 

In IIS instead of pointing to just the DotNetNuke Folder, you should point the virtual directory to C:\Dotnetnuke\website  that should take care of the issue!!


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
8/14/2007 8:48 AM
 

In this case the root folder is the website folder.

I suggest you go with the install package for this reason, you only have what you need.

 Especially for a production site.


Jim www.walkspoiled.com
 
New Post
2/18/2008 1:14 PM
 

Mitch Sellers wrote

In IIS instead of pointing to just the DotNetNuke Folder, you should point the virtual directory to C:\Dotnetnuke\website  that should take care of the issue!!

 

This clued me in to my problem: you don't want to name your DNN subdirectory the same as your configured virtual directory in IIS.  I had named them both "portal", and it didn't work well.  My pages loaded, but MS Visual Studio gives you the aforementioned compile error when you build the site.  I have web.config pages in my root, and several other subdirectories.  Multiple web.config files work OK, as long as you have them in the right place and have your virtuals set up correctly.

In short, renaming the folder "dnnportal", and leaving the virtual directory as "portal" solved this problem for me.

 

 
New Post
2/18/2008 1:42 PM
 

Sebastian Leupold wrote

make sure, there is no web.config in a parent folder.

IIS and/or Visual Studio re-create a root-level web.config when you remove it.  How to keep this from happening?

(I'd previously posted that my problem was solved - it is not). 

 
New Post
10/6/2008 10:12 PM
 

I had recently received this error when I in-advertently copied the web.config file into a subfolder of the root.

Rich

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error - allowDefinition=Error - allowDefinition='MachineToApplication'


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