This project has moved and is read-only. For the latest updates, please go here.

DotNetNuke Azure Accelerator 6.4

Rating:        Based on 1 rating
Reviewed:  1 review
Downloads: 371
Change Set: 22495
Released: Mar 24, 2013
Updated: Mar 25, 2013 by davidjrh
Dev status: Stable Help Icon

Recommended Download

Application DotNetNukeAccelerator 6.4
application, 42502K, uploaded Mar 25, 2013 - 371 downloads

Release Notes

Windows Azure deployments of DotNetNuke Community using virtual hard drive (cloud-drive) image that is created dynamically on the cloud. Enables the creation of new DotNetNuke host instances from on-premise to the cloud using a wizard that guides you on this process, creating the SQL Azure database, uploading the solution engine and associated service configurations.

New features in this release

New Features
  • Changed the packages to use OSVersion=3 by default: Windows Server 2012 and IIS 8
  • Added Support for active and passive FTP. You can enable it in the wizard on the remote option settings step
  • Added a new package supporting co-located cache. Note that you still will need a DNN caching provider that implements it.
  • Changed IIS 8 settings to use site pre-load
  • Changed the appPool Startup mode to AlwaysRunning (see this for more info)
  • Modified all the packages to support High Availability: now you can safely increase or decrease the number of role instances serving the website. The VHD drive will be dinamically attached, shared and connected between all the workers. The process will recover from failures when the VM acting as SMB server goes down for whatever reason.
  • Support for App_Offline to do safer DNN upgrades stopping incoming webrequests. When you change the configuration setting "AppOffline.Enabled" to "true", the site will appear as offline but will be published on port 12242. You can then run the upgrade on that port (portal aliases will be dinamically added). After finishing the upgrade, set the "AppOffline.Enabled" to "false" to re-enable the site.
  • App_Offline file can be customized by dropping an HTML file on "/Portals/_default/App_Offline.htm
  • Added a new step in the wizard to setup SSL configuration, allowing to upload the SSL certificate and CA's certificates
  • Now you can reload the packages in the wizard without having to restart the process
  • The last subscription used will be the default one when launching again the wizard


Getting started

The summary of steps for deploying DNN Community on Windows Azure is:
    1. You can sign-up for a free 3 month trial here
    1. Download the DotNetNuke Wizard Accelerator package and uncompress it
    2. Run DNNAzureWizard.exe and follow the steps

Reviews for this release

This makes deploying DNN to Azure so much easier, job well done. I did run into a few minor bumps the first time I tried but chose some different settings the second time and was up and running with a DNN site on Azure in about 10 minutes.
by beckerben on Jun 22, 2013 at 3:17 PM