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 ...New Installation QuestionNew Installation Question
Previous
 
Next
New Post
1/11/2008 10:33 AM
 

I am going to be installing the latest version of DNN on a Windows 2003 servers and I plan on using the DNN Installer Utility.  However, I am not going to want a virtual directory named "dotnetnuke", because I don't want that in the URL I give to my users to access DNN.  I want them to be able to use something like "http://myintranet/DocumentPortal".

When using the Installer utility, will I be able to accomplish this, or am I forced to created the DNN virtual directory?  If that must be created, can I still use a different VD for my users to access? If so, are there instructions on configuring this?  When I installed on my dev box, I used the dnn virtual directory.  One of the first lines in the "CleanInstall" readme installation instructions file is "- create Virtual Directory in IIS called DotNetNuke which points to the directory where the DotNetNuke.webproj file exists )".  Is this actually required, or can we name this Virtual Directory anything?

On my Dev box, I tried creating another VD in IIS and pointing that to my DNN installation, but got an error in the config file.  Is there a specific document or thread I can goto for information on this?  Thanks.

 
New Post
1/11/2008 7:09 PM
 

No, you can a name of your own choosing for your virtual directory.  You can also use any domain name that you own to point to it.  You can also pick a name for your DotNetNuke database

I assume that the problem you mentioned with your installation had to with some mis-configuration.  Without seeing your installation, though, it's impossible to tell you how to fix it.




Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...New Installation QuestionNew Installation Question


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