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 ...Convert ApplicationConvert Application
Previous
 
Next
New Post
8/21/2015 7:00 PM
 

In the instructions for installing DNN Platform:

http://www.dnnsoftware.com/wiki/how-to-install-dotnetnuke

1) It makes a bad assumption that I have a default website, and that even if I did, I would want DNN installed beneath it.

2) It installs DNN into a subdirectory of the site. Why would I want to do that?

3) It has all this stuff about converting the object into an application. With point #1, since I'm not adding it to any "default" site and am simply placing the files at the root of the site, I have no idea whether that's an "application" by default and, if not, what I would even need to "add" as an application (e.g. in the right-click > Add Application... dialog). While I've spent the last while reading up on the distinctions between the site, applications, and virtual directories, that still doesn't help clarify how they all interact in relation to being an actual website that in the end uses URLs and such and uses http to talk back and forth between clients and the server.

i.e. If DNN is the primary platform of my website, why on Earth would I want to set my website up so its platform is in a subdirectory and therefore have to monkey around with redirecting all requests for the root to a subdirectory? I'm sorry. This makes no sense to me without further information, and I'm finding nothing that outright spells out variations from the get-go.

So, if not installed in "default" website, and not installed in a subdirectory, do I need to mess with the "convert to application" step?

An extra point: it's super obnoxious that Web Platform Installer will only proceed through the installation with an apparent requirement to use SQL Express. No thanks. Am I supposed to know that DNN will later ask to set up a different DB connection? And if so, why would I want any extra baggage created somewhere in the meantime in relation to SQL Express if I have no intention of using it?

 
New Post
8/22/2015 4:47 AM
 
You may simply create a new website in your IIS using an app pool with ASP.NET 4 in integrated pipeline mode and unzip all files into it. Grant file system permission for the website folder to the ASP.NET user, specified in advanced settings of your App Pool.
If not using SQL Express or want to access your database with tools like SSMS, you'll need to create a blank database and a login granted dbowner permission on it.
Unblock downloaded install zip file and unzip into your IIS website folder. Bind the desired domain address(es) to your website and browse it to trigger the DNN installer.
That's it :)

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/24/2015 11:40 AM
 
Sounds as simple as it should. Thank you.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Convert ApplicationConvert Application


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.