Skip to main content

DNN (DotNetNuke) 05.02.00 Released - Highlights of Major Changes

DotNetNuke Community Edition Version 05.02.00 is now released. The complete details for all of the changes can be found in the ChangeLog.

 

Major Highlights

  • Added Module Information to the Help page
  • Added ability to view and edit the source files for a module
  • Enhanced the module creation wizard to simplify creating new module definitions
  • Added the ability to automatically create a test page as a step in the module creation wizard
  • Added a core API to support content localization
  • Added the ability to import/export page and module settings
  • Added the ability to immediately run a scheduled task
  • Added module caching provider API
  • Converted existing module caching feature to use new provider
  • Added page output caching provider API
  • Fixed issue where upgraded sites do not properly set the default Language
  • Fixed issue where scheduler could execute a a long-running task multiple times
  • Fixed issue where improperly formatted email addresses could result in error when sending system emails
  • Fixed issue which resulted in incorrect URL for SiteMap in a child portal
  • Fixed issue which caused error when deleting files from the Host file manager.
  • NOTE: System requirements have changed in DotNetNuke 5.2.0. DotNetNuke requires SQL Server 2005 or above and .NET 3.5 SP1. Please upgrade SQL Server and .NET before installing or upgrading to DotNetNuke 5.2.0.

Download:

You can download it from Dotnetnuke website or using following download links.

I normally use Source Code Package as it gives me easy way & complete flexibility to change code. But in general you want to start with Install Package (shared hosting) or Microsoft Web Platform Installer (local machine or dedicated server). You will still able to change Skin related code whichever version you use. 

 

Microsoft Web Platform Installer

Easy to install Microsoft Web Platform Installer Wizard
Install Package

Contains only the files needed for a run-time deployment to a web server. Download the Install Package if you want to deploy a live site to a web server with the minimum required files.

Upgrade Package

Contains only the files needed for upgrading an existing installation (does not include module packages). Download the Upgrade Package if you want to upgrade an existing installation to a newer version.

Source Code Package Contains everything including full application source code. Download the Source Package if you are a web developer interested in the DotNetNuke web application framework source code.
Visual Studio Starter Kit This MSI installs Visual Studio Templates for creating websites, modules and skins in Visual Studio. Download the Starter Kit if you are a web developer interested in creating skins or modules for the DotNetNuke web application framework using Visual Studio.

For larger organization who are using Dotnetnuke for business-critical application should also consider buying Professional, Elite and Elite Premier Editions. Elite and Elite Premier Editions is additional support on top of DotNetNuke Professional Edition codebase.

 

Reference Links:

DotNetNuke Professional Edition

Pro Edition Information

Compare Editions

Community Edition Quick Administration Guide

Quick Admin Guide

Installation Instructions

DotNetNuke Download Page

Watch a recording of the DotNetNuke Installation webinar.

DotNetNuke Installation Webinar Recording

Comments

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then you do not get

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs.   25 Best Blogs of 2009     25 Best Blogs 2008   25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog Deadspin: Spor

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck