Friday, May 26, 2017 Register    Login
 DNN v3 Links Minimize

  
 DNN Forum Threads Minimize

  
 DNN v3 Developer Minimize

  
DNN v3 Info - What's New  DNN v3 Info - What's New Minimize
DNN v3.1.0 Update Released - Sunday, June 12, 2005
An update to the DNN v3 release is out - read all about it here. This version contains many bug fixes and a couple of big enhancements. It also comes with a new installation procedure - be sure to follow the installation instructions in the zipfile you download! read more ...
DNN v3.0.13 (Release) Info Updated - Tuesday, May 31, 2005
I've updated the summary info below for the release version of DNN v3. Most of the changes in the release are incremental from the beta process - but portal upgrades are now officially supported! Stay tuned for more info to come! 
DNN v3.0.11 (public beta 8) Summary Info Updated - Thursday, February 24, 2005
I think I caught this version just as they were posting it - most mirrors I checked didn't have a copy of the zipfile yet :) I've added a Breaking News section below for a few changes I've noticed in the new beta. Too bad it's still not the RC... read more ...

Syndicate   Print   
DNN v3 Introduction  DNN v3 Introduction Minimize

Breaking News - the v3.1.0 Release is Here!
The core team has released DotNetNuke v3.1.0, and did it while they were at TechEd 05 in Orlando! Major changes in v3.1.0:

Visit the site and you'll see there's a new logo and site design on DotNetNuke.com - looks really nice! The site continues to evolve and get better organized to better serve the community.

WARNING: read the installation instructions for this upgrade!!
You can find the installation instructions here: \Documentation\Public\DotNetNuke Installation Guide.doc inside the distribution zipfile. The gist of it is that the MachineKeys (cryptography keys for the membership database) are now generated for each machine on a clean install. You must make a backup copy of your current web.config file and copy the SQL connection string info (and any other custom settings) into the new release.config file before renaming it to web.config. If you fail to copy over your machine keys, your users (including you) won't be able to login. See my installation notes for more information.

I've with every beta version of DNN v3 since v3.0.4 (the first v3 public beta, released November 2004), and most recently I've been doing a lot of custom module development in preparation for my MSDN Webcast series on DNN. This production v3 release is a great product with a tremendous number of functional changes and enhancements, usability improvements, and significant core reorganization. Much has changed, both for portal administrators and for custom module developers. See my New Features Summary page for a synopsis of what's new.

I can finally recommend with the v3 production release that you consider upgrading your v1 and v2 DotNetNuke sites to v3. Unless you've used only the standard modules, however, your upgrade path will likely be challenging. Watch for my upcoming Upgrading to V3 notes for some tips and pointers. There are a steadily-increasing number of v3 modules available, both free and at a modest cost - so you should be able to find replacement modules if your v2 module providers are slow moving to the new version.

If you haven't already, I encourage you to install v3 on a development machine and begin exploring it. This way you can get a good feel for how the latest version works and the changes since v2. It's also good practice to try upgrading using a backup of your current site. Please post your experiences in the DNN forums for all to learn from, especially if you find bugs or other problems with this process. That's the community spirit that DNN is built on!


Syndicate   Print   

 My v3 Bitch List Minimize
  • My biggest issue with v3 is that the page layout (at least with my skin) frequently gets screwed up when I edit the contents of a module, then save. The page turns into one continuous pane with all my modules listed sequentially down the length of the page. I haven't lost any data that I know of, but it's very annoying when I'm trying to update site content. 

  • User accounts cannot be shared across portals because of the Whidbey Membership provider. There's some discussion about this in the DNN forums. This isn't really a bitch - I just wish it wasn't so!

  • It would be very nice if the DNN distribution came in two flavors - the full source version, and one that contained only the runtime files needed to deploy DNN to a site. This would ease the deployment process for many people, without putting the full source code on their production site. This problem applies to all versions of DNN.


Syndicate   Print