It has been almost 3 years since I got my last cell phone, a Blackberry 8800. While it was nice, the UI was very sparse, and dare I say ugly. Ever since the Palm Pre was announced earlier this year, I have been itching to get one. Unfortunately, they are not available on my current provider. My wife, her parents, and I all share a family plan on the T-Mobile network which allows us to keep our cell phone charges way down so if I was going to get a new phone, it would have to be one that T-Mobile offered. When my wife's phone suddenly died 3 weeks ago, we started looking at new phones and finally settled on the new MyTouch phones from T-Mobile. My wife does not use 90% of the features on her phone because she finds it a bit challenging to figure out. To help solve this problem, we both decided to get the same phone, so that I would be able to help her out if she had any questions or issues.

More...

DotNetNuke 5.1.1 is now available for download.  This version of DotNetNuke is a stabilization release and focused exclusively on fixing outstanding bugs which did not make the cutoff for DotNetNuke 5.1 or which were discovered after 5.1 was released.  As many people in the community are aware, DotNetNuke.com had some difficulty running DotNetNuke 5.1 under extremely heavy loads.  As a result of that experience the DotNetNuke engineering team was able to isolate several performance issues which did not show up in any of the prior testing.  Fixes for those issues were incorporated in this release along with the changes outlined below.  As usual, the complete details for all of the changes can be found in the ChangeLog.

More...

DotNetNuke has a lot of great features that come built-in, but there are often situations where the default implementation is not what the customer wants for their website.  This was a big limitation of early versions of DotNetNuke – changing basic functionality often required the user to customize the core DotNetNuke code. 

In DotNetNuke 2.0 all of that began to change with the introduction of Providers in the framework.  This is also where we began focusing on a rich extensibility model that would allow users to install skins, skin objects, and modules as separate packaged extensions.  Over time, the framework has evolved to include different extension types, and in DotNetNuke 5.0 we moved to a unified extension model that treats all extension types in a similar manner during the install and uninstall process.

One of the extension types that was added in the last couple of years was the Authentication Provider.  Unlike most other providers, an authentication provider is not configured in the web.config and actually looks and behaves more like a module than an actual provider. 

More...