dnnazureaccelerator Releases Rss Feed

Updated Release: DotNetNuke Azure Accelerator 6.4 (mar 24, 2013)

davidjrh — Sun, 24 Mar 2013 23:29:52 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx 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

Fixes

Fixed an issue causing the website not being started after restarting an instance (see http://technet.microsoft.com/en-us/library/dd316029(v=ws.10).aspx for more info
Fix for gracefully exiting from Startup Tasks (see http://dnnazureaccelerator.codeplex.com/discussions/435387)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Released: DotNetNuke Azure Accelerator 6.4 (Mar 24, 2013)

Sun, 24 Mar 2013 23:29:52 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx 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

Fixes

Fixed an issue causing the website not being started after restarting an instance (see http://technet.microsoft.com/en-us/library/dd316029(v=ws.10).aspx for more info
Fix for gracefully exiting from Startup Tasks (see http://dnnazureaccelerator.codeplex.com/discussions/435387)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4 (mar 24, 2013)

davidjrh — Sun, 24 Mar 2013 18:47:52 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx 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

Fixes

Fixed an issue causing the website not being started after restarting an instance (see http://technet.microsoft.com/en-us/library/dd316029(v=ws.10).aspx for more info
Fix for gracefully exiting from Startup Tasks (see http://dnnazureaccelerator.codeplex.com/discussions/435387)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4 (mar 24, 2013)

davidjrh — Sun, 24 Mar 2013 18:46:31 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx 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

Fixes

Fixed an issue causing the website not being started after restarting an instance (see http://technet.microsoft.com/en-us/library/dd316029(v=ws.10).aspx for more info
Fix for gracefully exiting from Startup Tasks (see http://dnnazureaccelerator.codeplex.com/discussions/435387)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4 (mar 24, 2013)

davidjrh — Sun, 24 Mar 2013 17:49:52 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx 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

Fixes

Fixed an issue causing the website not being started after restarting an instance (see http://technet.microsoft.com/en-us/library/dd316029(v=ws.10).aspx for more info
Fix for gracefully exiting from Startup Tasks (see http://dnnazureaccelerator.codeplex.com/discussions/435387)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Released: DotNetNuke Azure Accelerator 6.4 (Mar 24, 2013)

Sun, 24 Mar 2013 17:49:51 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx 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

Fixes

Fixed an issue causing the website not being started after restarting an instance (see http://technet.microsoft.com/en-us/library/dd316029(v=ws.10).aspx for more info
Fix for gracefully exiting from Startup Tasks (see http://dnnazureaccelerator.codeplex.com/discussions/435387)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4

davidjrh — Sun, 24 Mar 2013 17:47:24 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx for more info)
Modified all the packages to support High Availability: now you can safely increase or decrease the number of roles 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

Fixes

Fixed an issue causing the website not being started after restarting an instance (see http://technet.microsoft.com/en-us/library/dd316029(v=ws.10).aspx for more info
Fix for gracefully exiting from Startup Tasks (see http://dnnazureaccelerator.codeplex.com/discussions/435387)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4

davidjrh — Sat, 23 Mar 2013 20:47:09 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx for more info)
Modified all the packages to support High Availability: now you can safely increase or decrease the number of roles 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

Fixes

Fixed an issue causing the website not being started after restarting an instance (see http://technet.microsoft.com/en-us/library/dd316029(v=ws.10).aspx for more info
Fix for gracefully exiting from Startup Tasks (see http://dnnazureaccelerator.codeplex.com/discussions/435387)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4

davidjrh — Sat, 23 Mar 2013 20:46:21 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx for more info)
Modified all the packages to support High Availability: now you can safely increase or decrease the number of roles 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

Fixes

Fixed an issue causing the website not being started after restarting an instance (see http://technet.microsoft.com/en-us/library/dd316029(v=ws.10).aspx for more info
Fixed for gracefully exiting from Startup Tasks (see (see http://dnnazureaccelerator.codeplex.com/discussions/435387)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4

davidjrh — Sat, 23 Mar 2013 20:39:39 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx for more info)
Modified all the packages to support High Availability: now you can safely increase or decrease the number of roles 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

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4

davidjrh — Sat, 23 Mar 2013 20:30:29 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx for more info)
Modified all the packages to support High Availability: now you can safely increase or decrease the number of roles 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

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4

davidjrh — Sat, 23 Mar 2013 20:29:24 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx for more info)
Modified all the packages to support High Availability: now you can safely increase or decrease the number of roles 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.
AppOffline file can be customized by dropping an HTML file on "/Portals/default/App_Offline.htm

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4

davidjrh — Sat, 23 Mar 2013 20:19:28 GMT

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 http://blogs.msdn.com/b/vijaysk/archive/2012/10/11/iis-8-what-s-new-website-settings.aspx for more info)

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.4

davidjrh — Sat, 23 Mar 2013 20:11:24 GMT

New features in this release

New Features

lore ipsum

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Created Release: DotNetNuke Azure Accelerator 6.4

davidjrh — Sat, 23 Mar 2013 16:00:55 GMT

New features in this release

New Features

lore ipsum

Updated Release: DotNetNuke Azure Accelerator 6.3 (oct 08, 2012)

davidjrh — Tue, 09 Oct 2012 09:03:20 GMT

New features in this release

New Features

Added a new startup task to setup and configure the localhost SMTP server on the webroles. Now you can use LOCALHOST as SMTP server without the need of using a 3rd party SMTP server
Added "post-install" addons feature: if an url pointing to a .zip file is specified in the service configuration file, after the successful start of the SMB server the .zip file will be downloaded and decompressed into the DotNetNuke folder maintaining the same files and folder architecture and overwriting contents. This is an useful feature to add in an automated way 3rd party files, dependencies, etc. to a DotNetNuke clean install. Use it as you wish.
Added SSL binding support: the Accelerator wizard does not include a step to setup this yet, but the work is done in the package. To manually setup SSL on your service configuration file, please read this thread http://dnnazureaccelerator.codeplex.com/discussions/359504
Added Web Platform Installer support: a new startup task has been added to enable WebPI products installations and dependencies, like MVC3, WebDeploy, etc.
Added WebDeploy support: a new checkbox has been added in the Remote Desktop setup step, in order to enable WebDeploy. Using the new Web Plaform Installer feature, with Web Deploy enabled (note that enabling this feature takes about 10 more minutes for the VM deployment), you can access to your site using tools like WebMatrix or other command line tools like WebDeploy's command line utility, in order to copy or modify files or create your own backups.

Fixes

Changed the way to import the publish settings file: discontinued the automatic download while refreshing the subscription data, you have to manually download and import the file in the wizard.
The packages are using the latest Azure SDK 1.7 (June 2012)
Fixed the packageUrl on the SMB package
Fixed references to use latest versions
Fixed an issue causing the "fileshare" user's password being expired after a month
Fixed an issue on the wizard's verification step while deploying ("No deployments were found")

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Released: DotNetNuke Azure Accelerator 6.3 (Oct 08, 2012)

Tue, 09 Oct 2012 09:03:20 GMT

New features in this release

New Features

Added a new startup task to setup and configure the localhost SMTP server on the webroles. Now you can use LOCALHOST as SMTP server without the need of using a 3rd party SMTP server
Added "post-install" addons feature: if an url pointing to a .zip file is specified in the service configuration file, after the successful start of the SMB server the .zip file will be downloaded and decompressed into the DotNetNuke folder maintaining the same files and folder architecture and overwriting contents. This is an useful feature to add in an automated way 3rd party files, dependencies, etc. to a DotNetNuke clean install. Use it as you wish.
Added SSL binding support: the Accelerator wizard does not include a step to setup this yet, but the work is done in the package. To manually setup SSL on your service configuration file, please read this thread http://dnnazureaccelerator.codeplex.com/discussions/359504
Added Web Platform Installer support: a new startup task has been added to enable WebPI products installations and dependencies, like MVC3, WebDeploy, etc.
Added WebDeploy support: a new checkbox has been added in the Remote Desktop setup step, in order to enable WebDeploy. Using the new Web Plaform Installer feature, with Web Deploy enabled (note that enabling this feature takes about 10 more minutes for the VM deployment), you can access to your site using tools like WebMatrix or other command line tools like WebDeploy's command line utility, in order to copy or modify files or create your own backups.

Fixes

Changed the way to import the publish settings file: discontinued the automatic download while refreshing the subscription data, you have to manually download and import the file in the wizard.
The packages are using the latest Azure SDK 1.7 (June 2012)
Fixed the packageUrl on the SMB package
Fixed references to use latest versions
Fixed an issue causing the "fileshare" user's password being expired after a month
Fixed an issue on the wizard's verification step while deploying ("No deployments were found")

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.3 (oct 08, 2012)

davidjrh — Mon, 08 Oct 2012 16:19:33 GMT

New features in this release

New Features

Added a new startup task to setup and configure the localhost SMTP server on the webroles. Now you can use LOCALHOST as SMTP server without the need of using a 3rd party SMTP server
Added "post-install" addons feature: if an url pointing to a .zip file is specified in the service configuration file, after the successful start of the SMB server the .zip file will be downloaded and decompressed into the DotNetNuke folder maintaining the same files and folder architecture and overwriting contents. This is an useful feature to add in an automated way 3rd party files, dependencies, etc. to a DotNetNuke clean install. Use it as you wish.
Added SSL binding support: the Accelerator wizard does not include a step to setup this yet, but the work is done in the package. To manually setup SSL on your service configuration file, please read this thread http://dnnazureaccelerator.codeplex.com/discussions/359504
Added Web Platform Installer support: a new startup task has been added to enable WebPI products installations and dependencies, like MVC3, WebDeploy, etc.
Added WebDeploy support: a new checkbox has been added in the Remote Desktop setup step, in order to enable WebDeploy. Using the new Web Plaform Installer feature, with Web Deploy enabled (note that enabling this feature takes about 10 more minutes for the VM deployment), you can access to your site using tools like WebMatrix or other command line tools like WebDeploy's command line utility, in order to copy or modify files or create your own backups.

Fixes

Changed the way to import the publish settings file: discontinued the automatic download while refreshing the subscription data, you have to manually download and import the file in the wizard.
The packages are using the latest Azure SDK 1.7 (June 2012)
Fixed the packageUrl on the SMB package
Fixed references to use latest versions
Fixed an issue causing the "fileshare" user's password being expired after a month
Fixed an issue on the wizard's verification step while deploying ("No deployments were found")

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Released: DotNetNuke Azure Accelerator 6.3 (Oct 08, 2012)

Mon, 08 Oct 2012 16:19:33 GMT

New features in this release

New Features

Added a new startup task to setup and configure the localhost SMTP server on the webroles. Now you can use LOCALHOST as SMTP server without the need of using a 3rd party SMTP server
Added "post-install" addons feature: if an url pointing to a .zip file is specified in the service configuration file, after the successful start of the SMB server the .zip file will be downloaded and decompressed into the DotNetNuke folder maintaining the same files and folder architecture and overwriting contents. This is an useful feature to add in an automated way 3rd party files, dependencies, etc. to a DotNetNuke clean install. Use it as you wish.
Added SSL binding support: the Accelerator wizard does not include a step to setup this yet, but the work is done in the package. To manually setup SSL on your service configuration file, please read this thread http://dnnazureaccelerator.codeplex.com/discussions/359504
Added Web Platform Installer support: a new startup task has been added to enable WebPI products installations and dependencies, like MVC3, WebDeploy, etc.
Added WebDeploy support: a new checkbox has been added in the Remote Desktop setup step, in order to enable WebDeploy. Using the new Web Plaform Installer feature, with Web Deploy enabled (note that enabling this feature takes about 10 more minutes for the VM deployment), you can access to your site using tools like WebMatrix or other command line tools like WebDeploy's command line utility, in order to copy or modify files or create your own backups.

Fixes

Changed the way to import the publish settings file: discontinued the automatic download while refreshing the subscription data, you have to manually download and import the file in the wizard.
The packages are using the latest Azure SDK 1.7 (June 2012)
Fixed the packageUrl on the SMB package
Fixed references to use latest versions
Fixed an issue causing the "fileshare" user's password being expired after a month
Fixed an issue on the wizard's verification step while deploying ("No deployments were found")

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps

Updated Release: DotNetNuke Azure Accelerator 6.3 (oct 08, 2012)

davidjrh — Mon, 08 Oct 2012 14:50:44 GMT

New features in this release

New Features

Added a new startup task to setup and configure the localhost SMTP server on the webroles. Now you can use LOCALHOST as SMTP server without the need of using a 3rd party SMTP server
Added "post-install" addons feature: if an url pointing to a .zip file is specified in the service configuration file, after the successful start of the SMB server the .zip file will be downloaded and decompressed into the DotNetNuke folder maintaining the same files and folder architecture and overwriting contents. This is an useful feature to add in an automated way 3rd party files, dependencies, etc. to a DotNetNuke clean install. Use it as you wish.
Added SSL binding support: the Accelerator wizard does not include a step to setup this yet, but the work is done in the package. To manually setup SSL on your service configuration file, please read this thread http://dnnazureaccelerator.codeplex.com/discussions/359504
Added Web Platform Installer support: a new startup task has been added to enable WebPI products installations and dependencies, like MVC3, WebDeploy, etc.
Added WebDeploy support: a new checkbox has been added in the Remote Desktop setup step, in order to enable WebDeploy. Using the new Web Plaform Installer feature, with Web Deploy enabled (note that enabling this feature takes about 10 more minutes for the VM deployment), you can access to your site using tools like WebMatrix or other command line tools like WebDeploy's command line utility, in order to copy or modify files or create your own backups.

Fixes

Changed the way to import the publish settings file: discontinued the automatic download while refreshing the subscription data, you have to manually download and import the file in the wizard.
The packages are using the latest Azure SDK 1.7 (June 2012)
Fixed the packageUrl on the SMB package
Fixed references to use latest versions
Fixed an issue causing the "fileshare" user's password being expired after a month
Fixed an issue on the wizard's verification step while deploying ("No deployments were found")

Getting started

The summary of steps for deploying DNN Community on Windows Azure is:

GET A WINDOWS AZURE SUBSCRIPTION
1. You can sign-up for a free 3 month trial here http://www.windowsazure.com/es-es/pricing/free-trial/
RUN THE ACCELERATOR
1. Download the DotNetNuke Wizard Accelerator package and uncompress it
2. Run DNNAzureWizard.exe and follow the steps