I found some time to start testing the next release of DotNetNuke. While the public has access to a Beta build (5.1.0.266), our team can benefit from the latest checked in bits (Currently 5.1.0.321). After grabbing it from our source control tool, I could not install DotNetNuke, and this was a good thing because I learnt, from the solving process and from my fellow members, that the next version automatically sets itself to use .NET 3.5 if available.

Currently, the install package includes the .net 2.0 version of the System.web.extensions library. This version is located inside the website bin folder and is necessary to start the installation process, which uses AJAX for some of its steps.

After the install is completed, and if the server has .NET 3.5 installed, the assembly is removed and your site automatically configured to use the latest framework.

An informative link about a new feature
In the same vein, Twitter is the source of some of the most useful information I am finding both about DNN and other topics I am interested in. I had resolved to post about latest development in the DNN world, but it is not something I always find time to do. Of course, I won’t microblog here to avoid boring the community in general. However this post is already long enough to deserve a bonus shout out to a post about a new feature in DNN 5.1.

There’s a new module targeted at making it easier to manage websites and installs. Although it is a work in progress, it is also an example of the path DotNetNuke is taking. The post is at Learn MS .Net, but I could not find the author’s name. Written by Sam McDonald, it is a good read, with screens and some explanations.