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

DotNetNuke Azure Deployment Accelerator

Rating: No reviews yet
Downloads: 180
Change Set: 5662
Released: Feb 21, 2011
Updated: Jun 8, 2011 by davidjrh
Dev status: Stable Help Icon

Recommended Download

Application DotNetNukeRapidDeployment
application, 43921K, uploaded Feb 21, 2011 - 180 downloads

Release Notes

Windows Azure deployments of DotNetNuke Community using pre-configured virtual hard drive (cloud-drive) images. Enables the migration from on-premise to the cloud of application images, accelerator solution engine and associated service configurations. Provides for the migration of local Microsoft SQL Server or SQL Express database schema and content to SQL Azure; including the creation of accounts and logins necessary to enable, set or reset connectivity between the hosted service and SQL azure database.

A full working reference example of DotNetNuke Community 5.6.1 as an image, with a corresponding exported SQL schema is included. To get started, unzip the package, update the ServiceConfiguration.cscfg with settings for your Azure services, and then run the SetupDotNetNuke.bat file.

For more information about where to source the settings, and an overall view of what actions are automated, please see the rapid deployment diagram and checklist files. (Also included in the package download.)


Getting started

This accelerator is almost identical to the Umbraco Rapid Deployment Accelerator, so check the Diagram developed by Slalom Consulting. The summary of steps for deploying DNN Community on Windows Azure is:
    1. Create a Windows Azure Storage Services instance
    2. Update the .cscfg file AccountName and AccountKey for AcceleratorConnectionString and DiagnosticsConnectionString
    1. Enable SQL Azure providing an username and password for the Administrator account
    2. Update .cscfg database Setting with Server, Admin Username, Admin Password, DB Username and DB Password (the DB user is the user that will be created by the scripts and will be the DBO of the database in production)
    1. Start SetupDotNetNuke.bat (ensure that you have saved the changes made to the ServiceConfiguration.cscfg in 1.2) and 2.2). Wait for the successful completion of the following automated processes -you should want to edit the .bat file in order to comment/uncomment steps to check that everything is going fine:
      1. DotnetNuke database creation
      2. User and security database configuration
      3. DotNetNuke Azure-friendly SQL schema deployment
      4. DotNetNuke pre-configured site data load
      5. Upload of the ServiceConfiguration.cscfg
      6. Upload of the dotnetnuke.config file for the accelerator configuration
      7. Upload of the Service.cspkg accelerator solution engine (3Mb)
      8. Upload of the Cloud Drive (dotnetnuke.vhd) to a Blob container (256Mb)
    1. Create a Windows Azure Hosted Service instance
    2. Add a new Production Deployment, selecting the package and configuration files from Windows Azure Storage (uploaded by the automation scripts in 3.1.5 and 3.1.7
    3. Start the service
    1. Home page:
    2. Change the "admin" and "host" passwords ("dnnadmin" and "dnnhost" by default)

Known Limitations

  1. Since the accelerator uses the HWC (Hostable Web Core) that does not support Framework 4.0, the Razor Host module will not work in this version. You will see the module available in the default installation but you will encounter an error loading the module if you add it. I'll check for a workaround until the next HWC version arrives.

Reviews for this release

No reviews yet for this release.