Since the release of DNN 3.2 and DNN 4.0, I have been testing all of my modules. Everything worked as planned except I was having troubles uploading the Aggregator and Module Rotator module in DNN 4.0. The error I was getting was  ExceptionSystem.ObjectDisposedException: Cannot access a closed file. at System.IO.__Error.FileNotOpen(). The solution that seems to work is to add the requestLengthDiskThreshold attribute to the httpRuntime in web.config.

 requestLengthDiskThreshold="8192" />

Since getting that upload problem worked through, I've been able to test in DNN 4.0 and all of the modules are working fine. If anyone has a problem installing anything, please provide details and post in the forums and we'll see what we can do to help you out.

In the move to DotNetNuke 3.x, the core team has decided to support the new membership provider API that Microsoft is introducing in ASP 2.0. The new model brings enhanced functionality and extensibility to DotNetNuke, but it also removes much of the profile data from the Users table to a new table named aspnet_Profile. This has essentially removed access to this data from SQL queries and joins because it is no longer stored in individual fields like in DNN 2, but now resides in a blob type field instead. This article will show you how to get it back !

Well, it was a little off target but the first public beta of DotNetNuke 3.0 (3.04 actually) is finally out. I've been testing the previous betas in the 30 for 3.0 program and I can tell you first hand that the core development team has done a fantastic job in moving this ahead. There are many, many enhancements for both users and developers in this release.

I will post updates to all my components as soon as I can. Because of the namespace changes and other things, none of the 2.x components you have will work in DNN 3.0 without changes.

Well, it looks as though the next version of DotNetNuke will be a major release instead of a point release and will be version 3.0 instead of 2.2.

Here are a few links to whet your appetite.

DotNetNuke 3.0 - Announcement
DotNetNuke 3.0 - Breaking Changes for Module Developers

Microsoft has released an ASP.NET HTTP module that Web site administrators can apply to their Web server. This module will protect all ASP.NET applications against all potential canonicalization problems known to Microsoft.

You can get this patch here.

From Scott McCullough, a member of the DotNetNuke team.

No guarantees, but :-

We have given ourselves a "code complete" date of October 15 and an initial release date of November 1. From 10/15 - 11/1 we'll be in full-tilt-debugging and fixing mode!

Last night I decided to bite the bullet and upgrade to DotNetNuke 2.1.2. Everything went pretty smoothly so I decided I would share my approach. If you notice anything odd with the site, please let me know at support@dnnstuff.com

ADSIAdmin: ADSI Settings interface & all functions for DotNetNuke authenticated with Windows network. The component is released with full source code

ADSIImport: Import users/groups from Windows Active Directory into DNN database.

These features are implemented in a separate custom module (private assembly). Supports User Principal Name (UPN) format when user logon in Form Authentication against AD mode. Option for admin to choose if user's group membership to be synchronized anytime user logs on.

Register first at TTT Company and then you will have download access.

OK, so admittedly calling this one a “HOWTO” may be giving the snippet delusions of grandeur. At best, it's a tip -- at worst, it's something self-evident that everybody knows already :)

However, since I had to look it up I thought I might save at least one other person the trouble. To add a menu break (those little horizontal separator bars you see in regular Windows menus) to an Action menu, just do the following:

With MyBase.Actions
.Add(GetNextActionID, "~", "")
End With

A quick example of the trivial syntax for handling Action menu events in the same module in which they're raised, without having to dig through the core to figure out how.

There seems to be a bit of a boggle with the 2.1.1 release. A binary incompatibility with HostSettings is causing some PA's built against earlier versions to have problems with the newest release. Wait until the patch comes out in a couple days to upgrade your sites. It's probably not a bad idea to wait a week or so after any of these releases before upgrading any live sites just in case. Here are the details.

DotNetNuke 2.1.1 is now available at the mothership. To get the latest release either register or log in with your current username and password and go to the download section.

There are some nice new features in this new version including Event Logging, Rich Text Editor mods, Scheduler and System Messages. I'll be looking into these more thoroughly as I upgrade the site to the new version.