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 connetivty between the hosted service and SQL azure database.
A full working reference example of DotNetNuke Community 5.6.2
as an image, with a corresponding exported SQL schema is included. To get started, unzip the package and start the DNNAzureWizard.exe. Review the Getting Started section
New features in this version
- Support for Windows Azure SDK 1.4 (April refresh)
- Support for .NET Framework 4.0 (so Razor is also supported)
- Remote Desktop to the instances
- Possibility to use Azure Connect
- Web.config modification supported (the files are in a shared read/write cloud drive)
- Multiple portal alias are also supported
- DNN Community 5.6.2 image included and preconfigured as a WebFarm (filecachingprovider is used for CE)
This accelerator is almost identical to the Umbraco Rapid Deployment Accelerator, so check the Diagram developed by Slalom Consulting
. The SMB version has been inspired by a blog post of Dinesh Haridas
that you may also read to understand the background.
The summary of steps for deploying DNN Community on Windows Azure is:
- PROVISION STORAGE SERVICES
- Create a Windows Azure Storage Services instance
- PROVISION SQL AZURE
- Enable SQL Azure providing an username and password for the Administrator account. Enable access for Windows Azure services in the firewall settings.
- START DEPLOYMENT PROCESSES
- Start DNNAzureWizard.exe and follow the assistant instructions. Wait for the successful completion of the following automated processes -you should want to edit the "bin\DeployDotNetNuke.bat" file in order to comment/uncomment steps to check that everything is going fine:
- DotnetNuke database creation
- User and security database configuration
- DotNetNuke Azure-friendly SQL schema deployment
- DotNetNuke pre-configured site data load
- Upload of the ServiceConfiguration.cscfg
- Upload of the DNNAzureSMB.cspkg accelerator solution engine (6Mb)
- Upload of the Cloud Drive (dotnetnuke.vhd) to a Blob container (256Mb)
- PROVISION HOSTED SERVICE
- Create a Windows Azure Hosted Service instance
- 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
- Start the service
- Home page: http://yoursite.cloudapp.net/default.aspx
- Change the "admin" and "host" passwords ("dnnadmin" and "dnnhost" by default)
DNNAzure Single and ExtraSmall
There is also a package for simplified scenarios that should be ideal for the use of promotinal offers of free ExtraSmall instances. In this package, a DNNAzure webrole (the "Instance 0") assumes the work of the SMB server, mounting and sharing the cloud drive
Enabling Remote Desktop
To enable remote desktop to the instances, you'll need to rebuild the DNNAzureSMB.cspkg in order to include your credentials. Check this guide
that describes this process.
- The DNN Azure Accelerator (SMB version) can only use one instance for the SMB worker role (you can add web roles as needed), so high availability is not covered yet. A warning message will appear when you deploy the service.