As a developer of hundreds of custom DotNetNuke extensions I have to say one of my favorite enhancements to the DotNetNuke platform over the last few years was the inclusion of the new DotNetNuke Form Pattern that was part of the 6.x release.  By incorporating a consistent design pattern it became trivial for extension developers to build modules that had similar UI patterns and would thus have consistently styled applications.  By doing this it is possible to make the understanding of flow within your applications easier as you are leverage a UI style that more similarly matches that of the platform itself.  However, as with any new feature it hasn't came without a few "bumps" in the road.  There were a few changes between 6.x and 7.x that have caused a bit of a problem for those of us that have already adopted the patterns, or those that might.  In this post we will look at these differences and the one small change that you can make for a seamless experience regardless of if you are targeting 6.x or 7.x!

I’m pleased to announce that we have just released a Community Technology Preview of DotNetNuke 7.1.  We have many new features on the way that are sure to get you excited.  This CTP release will highlight a few of the key areas that we would like members of our community to test and provide feedback.  Keep reading to learn about the new features in DotNetNuke 7.1 CTP.

Securing the login of your DotNetNuke site is very important, but often neglected for the wrong reasons. It shouldn’t be because SSL adds a performance overhead to your site. It shouldn’t be because SSL certificates are expensive either. But most of all, it should not be because it is hard!

It has now been a little over 4 years since we announced the availability of a professionally supported commercially licensed edition of the DotNetNuke platform. The introduction of a commercial version was done in an attempt to find a sustainable business model; a model which could provide us with the resources we need as project steward to accelerate development and adoption of the platform, as well as preserve and strengthen the symbiotic relationship between all of the stakeholders in our open source community.

This version, 06.01.01, is a release that has very important new options: anonymous enrollment & integration of the DNN social API/Journal, in addition to a number of bug fixes, enhancements and changes.

The error can occur due to number of things e.g. an unclosed tag (particuaraly a FORM tag), or some other piece of content that cannot be encoded, or the number of parameters

BigData – it seems to be a technology area that is in vogue.  It encompasses technologies such as Hadoop, Hive, Pig and Sqoop – yes they all seem to have funny names. 

Every quarter, in the Engineering dept. at DotNetNuke Corp, we have quarterly reviews where we review with our manager the previous quarter’s objectives and establish objectives for the upcoming quarter.  At the beginning of this year one of my objectives was to become more familiar with these BigData technologies and determine which if any we at DNN need to be aware of.

This is my first outing here at DNN blog central so to get my blogging off to a start I’m covering a topic near and dear to my heart, which is the combination of DNN sites and SEO.  

This blog entry is all about 5 common SEO mistakes that are made and how DNN can be used to fix those.  Read on to find out if you're making any, and how your DNN site can save you if you have.

The 7.0.6 CE, PE and EE versions of DotNetNuke have been released. The release notes can be found here

These releases fix one security issue, rater as "low".

Over the past few months I ran into the same issue with DotNetNuke 6 websites quite a few times: “I can’t login on my DotNetNuke 6 website with Internet Explorer 10!”

And because Windows 8 ships with Internet Explorer 10 (IE10), and since DotNetNuke 6 websites will not all be upgraded to 7 anytime soon, chances are this issue will become increasingly annoying.

Please join me in welcoming your DNN★MVP’s for Spring 2013!

You should already be aware, but there is an incredibly active and vibrant user group in Charlotte, North Carolina called Queen City DotNetNuke User Group or QCDUG.  These folks were also the masterminds behind the Day of DotNetNuke Charlotte last year.  When they agreed to do another event this year, I couldn’t even tell you how excited I was because last year was so awesome!  These gentlemen sure did not disappoint when they organized and held their second event, this time branded in a fun way as Southern Fried DNN!  What a great way to participate in our community!

We are the largest open source project in the Microsoft Ecosystem. 

7.0M+ Downloads; Hundreds of thousands of sites; 1.0M+ Registered Members; 2200 Product Subscription Customers!

Bank of America, Time Warner, Aviva, SportsDirect, Department of Defense – DOD (over 160 web properties), Sears, etc.

We are renowned for helping organizations “manage content”.  Why not also help them “manage communities”? 

This post will provide you with a basic tutorial for utilizing SignalR with custom DotNetNuke Modules. If you want to bypass the blog post go check out the source on GitHub, you can Fork my Repository. The module created here will be very simple, if you want a full blown module with more features be sure to check out the open source DotNetNuke Module SignalRChat, and see it in action at http://dnnCHAT.com/

SignalR is an ASP.NET library for using websockets and long polling in your applications. Basically what this means, is that you can have your web pages (or apps) maintain an open connection with a webserver, passing data back and forth, without having to do standard posts and gets for the content and functions. SignalR is a free library that you can get from www.signalr.net and you can DL from nuget.org right into your Visual Studio projects.

The next release of the Active Directory provider is now available. This release contains only bug fixes that fix a couple of major issues that recently came to light.

One of the lesser known, but very powerful template options of the DotNetNuke DDR Menu, originally created by Mark Allan, is Razor. A while back, Joe Brinkman had a very interesting blog post, combining razor templating with taxonomy to come to very advanced menu layouts.
Sadly, DotNetNuke 7.0 introduced a breaking change in the way Razor was supported that specifically impacted the DDR Menu implementation of it. Although the issue had been on our radar for some time, it was not a very easy one to fix… Well.. the wait is over, in DotNetNuke 7.0.4, this is finally fixed.

Did you know that the DotNetNuke Community has a team on the micro-lending site Kiva.com? 

It’s another month and the DNN Corp team has a new release for you. On November last year we released DNN version 7.0.0 which included changes throughout the product, and with this release we’re taking care of many of

the issues and enhancements reported by our team and the community. 

DotNetNuke module development became a lot easier when it became easy to use MSBuild to simply build your project and get a nice install-able module package in the end.  I've been using this process for a number of years now, but there have always been those little things with the default templates that many have been distributing that just don't meet my needs 100%.  For example a few years back I blogged about a fix for Auto Packaging Multiple Modules.  This post shows a fix for one of my other biggest pet-peeves when it comes to the auto-package process and that comes from the determination of the 'PackageName' that is used to name the destination file.

Everything is better fried! Don’t miss the upcoming DotNetNuke Community conference in Charlotte, NC

A serious event: DNN Events 06.01.00 BETA is available!

This version, 06.01.00, is a release that does not have many new features, but does have very important big new options: anonymous enrollment & integration of the DNN social API/Journal, in addition to a number of small enhancements and changes.

Having been a Front-End Developer for years, I have a keen design eye, and love it when a partner does a great job of designing a site and especially when it gets implemented on DotNetNuke...

It is with a bit of sadness, and a bit of excitement that I put together this blog post. After February 15th I will no longer be an employee of DotNetNuke. I’ve been with the company almost 3 years (March 1st would have been my anniversary), and I’ve been working with the project for the past 10+ years and worked for one of DotNetNuke’s leading partners, Engage Software, for almost 6 years before starting with DNNCorp.

There’s really nothing bad I could possibly say about any code camp in Florida. Community leaders like Dave Noderer make such a thing impossible. They are so amazing in their ability to organize a fantastic event. South Florida Code Camp 2013 was just as amazing as this code camp always has been. This is about my 3rd or 4th time presenting here. It just gets better and better! This blog post is mostly about the resources for my sessions though.

Since today it was never so easy to build your DotNetNuke playground.