Archive
Monthly
Go
|
|
DNN Blog
Dec
26
Posted by:
Joe Brinkman
12/26/2008 10:03 AM
 Christmas Eve was very busy for the DotNetNuke Team as we did a double release of both DotNetNuke 4.9.1 and 5.0.0. This was my first time handling a double release and it was a lot more work than I anticipated. Not only did we do a double release, but we also changed where we are hosting our downloads. That is a story for another blog post. Unlike 4.9.1, DNN 5 was a massive change that involved hundreds of bug fixes, changes and enhancements. A large number of the bug fixes and a few of the changes were backported to the 4.8.x and 4.9.x branches, however there are still many bug fixes and enhancements which are only available in DNN 5. At this point there are not plans to port any other changes back to the DNN 4.x platform as we will once again shift our focus to maintaining a single product branch.
DotNetNuke 5.0 is the culmination of over a year of development and testing. Without a doubt this is the most tested version of DotNetNuke ever released. That is not to say there won’t be bugs found, but just that we spent a lot of time in this release trying to make sure we were not breaking anything in our efforts to refactor the codebase. As we have said many times in the past, DotNetNuke 5.0 is not intended to encompass the entire Cambrian Vision which we first laid out at OpenForce ‘07. However, DNN 5 does include many fundamental changes in the architecture which will make it much easier for us to incorporate and test future features. With that said, there are still a number of great enhancements that we were able to include in this release. As always you can see a complete list with all the details of each fix/change in the ChangeLog. Major Highlights - Added jQuery support to the core platform. jQuery will now be distributed as part of the DotNetNuke installation and will be available for use by module developers.
- Added support for Internet Explorer 8 Web Slices. Administrators can configure any module to use IE8 Web Slices including the ability to set time-to-live and expiration values.
- Removed distinction between admin modules and pages and normal pages. This allows administrators to easily delegate access to any portion of the application to any group of users.
- Updated the installation services to support manifest files for all extension types. Now skins, containers, providers and modules are all first class citizens that can be installed and uninstalled.
- Expanded XHTML, WCAG and ADA compliance.
- Refactored core to improve support for Unit Testing. Refactored several core classes to use interfaces and added a simple component factory to provide dependency injection support.
- Added ability to deny permissions in the permissions grid. This new feature extends the permission framework to give administrators greater flexibility in defining permissions.
- Added Widget framework. The new Widget framework allows you to quickly add JavaScript/html widgets to your site with very little effort. The framework supports the use of a simple object tag based representation which means you don’t have to know JavaScript in order to add the widgets.
- Added new Object notation for using skin objects in Skins. Skin designers will no longer need to include separate XML files when creating and packaging skins. No more funky “[SKINOBJECT]” tags littering your html. This significantly simplifies the process of creating skins and further opens up skin development to a broader group of designers. If you include a simple JavaScript reference in your HTML skin, you can even get a full WYSIWYG experience when designing your skin.
Security Fixes - Includes a rollup of all 4.x security fixes
Updated Modules/Providers The following modules and providers have been updated in the 5.0.0 packages. Please see the specific project pages for notes on what bugs or enhancements were corrected with each release. Providers Technorati Tags: DotNetNuke
11 comment(s) so far...
Re: DotNetNuke 5.0.0 Released
Joe, this seems interesting. I have just downloaded 5 and I'm going to play with it a bit. I do have one question about 5 and this may have already been answered somewhere else, but I'm a little behind on what has been going on with DNN the past year or so. I'm assuming 5 will be the version going forward and 4.x will be retired at some point. Is this an accurate assumption?
Thanks
Bruce
By Bruce Hopkins on
12/29/2008 3:44 PM
|
Re: DotNetNuke 5.0.0 Released
Just downloaded everything - I guess you guys thought that there would be less activity with a release over the christmas period.
I'll be doing a test upgrade later today.
Well Done
A+
Julian
By Julian Watt on
12/29/2008 3:44 PM
|
Re: DotNetNuke 5.0.0 Released
GREAT!!
By davidee on
12/29/2008 3:44 PM
|
Re: DotNetNuke 5.0.0 Released
This is great. I installed on my Dev machine and it is looking very good. I am about to build a new site and am trying to decide between rolling it out on 5.0 or 4.9.1. What is the compatibility story on 5.0? Will skins all work? I would love to see someone write up a blog that discusses the architectural changes in the new 5.0 codebase. Reading hundreds of bugs and enhancements gets confusing and sometimes people can miss the forest through the trees.
By joiseystud on
12/29/2008 3:44 PM
|
Re: DotNetNuke 5.0.0 Released
I have installed new version of DotNetNuke (5.0) in my host site: dnn.fobos.com
(Windows 2003/ SQL Server 2005). By the way it was update to version 4.9, and I did not find any problem in update process.
The first impressions are:
- web.config "system.codedom" section should be updated. I was not able to run LINQ examples until modified this section in web.config:
- Menu does not work in IE6 and Windows 2000 (only top menu row is visible) , but it is OK with Windows XP, Windows 2003 & IE7
- initial loading still slow
- "manifest" drop-down list in "Module Definitions" shows all available .dnn files two times
But, I was able to quickly creates some new modules and use existing VB.NET code from ASP.NET pages in DNN ASCX, so it seems really good working in .NET 3.5. All working examples are under "Development" menu option.
Thank you DotNetNuke team for hard work an Happy New Year!
By Val Skordin on
12/29/2008 3:44 PM
|
Re: DotNetNuke 5.0.0 Released
@Val
web.config - as 5.0 still supports ASP.NET 2.0 out-of-the-box we could not update web.config. However, there is a mechanism within 5.0 to "update" web.config by a simple click of a button so it does support ASP.NET 3.5
By Charles Nurse on
2/1/2009 5:16 PM
|
Re: DotNetNuke 5.0.0 Released
It would be extremely helpful if there were some supporting documentation for the new version. I'd like to see something on the widget framework specifically.
By Ed DeGagne on
2/1/2009 5:16 PM
|
Re: DotNetNuke 5.0.0 Released
Good job!
I have Problems with the “SizeWidget” and “TextSizeWidget”. I change the size, when I change the page, I see the default size, after a short moment, the size change to full size. Is there a way to change this effect?
By Martin.Egli on
2/1/2009 5:17 PM
|
Re: DotNetNuke 5.0.0 Released
Good job!
I have Problems with the “SizeWidget” and “TextSizeWidget”. I change the size, when I change the page, I see the default size, after a short moment, the size change to full size. Is there a way to change this effect?
By Martin.Egli on
2/1/2009 5:17 PM
|
Re: DotNetNuke 5.0.0 Released
My portal don't work after udating. During updating i have just one error:
00:00:12.078 - Installing Package File testModule_01.00.00_Install: Error!
But after updating i have such error when i try to login:
A critical error has occurred.
Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request.
Can somebody help me?
By Ya_Serhiy on
2/1/2009 5:18 PM
|
Re: DotNetNuke 5.0.0 Released
I just upgraded to 5.0 and I have got an error every step of the way.
Executing Script: 04.09.01.SqlDataProvider Error! (see 04.09.01.log for more information)
every script that had to execute to do with the SqlDataProvider had an error.
The web site i was upgrading was a live production web site Windows 2003, SQL SERVER 2005
Now i am lost, how do i revert back to my old version. Can i upload the 4.9 upgrade release over the top of the 5.0 i just uploaded to the server run the upgrade again. Will this install 4.9 again.
I am raging now, normally DNN works flawlesly every time, 10 months of hard work is almost wasted. I hope that their is an easy way to revert back to the previous version.
The upgrade has just completed, every other step finsihed except the all these
04.09.XX.SqlDataProvider
04.09.01.SqlDataProvider
Any advice will be greatly appreciated
By Patrick Lismore on
2/1/2009 5:18 PM
|
|