DotNetNuke

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!

Read more...

Comments (0)

Last week I was a trainer and a speaker at the Southern Fried DotNetNuke event that was held in Charlotte, NC.  This event was fantastic with a day of optional training on Friday and a series of sessions on Saturday in the format of a regular Code Camp event.  As I promised the attendees of my sessions I would be posting information and assets from these presentations here on this blog.  This posting is an overall aggregate with information on the two sessions and trainings, future blog postings will expand on the information contained within.

Read more...

Comments (2)

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.

Read more...

Comments (0)

So I've been promising for years to publish presentation materials after each of my events.  I've been working on so many different ways to handle this, and finally have came up with an easy way to share materials from my events. Thanks to SkyDrive, I can now easily embed the content while doing as much as I can to keep ownership of the content, so here is the first one! I'll be posting a bunch of others as well soon, all will be tagged under "Presentations". 

Read more...

Comments (4)

As a person that has either directly written or managed the creation of over 400 custom DotNetNuke extensions in the past few years, the DotNetNuke package process is still the one item that I will at times overlook.  Well, recently DotNetNuke released a utility to help those of us looking to ensure that our extensions meet all of the proper requirements for consistent installation.  

Read more...

Comments (0)

In the past I have blogged about various DotNetNuke performance and management issues, focusing on how to keep the Site Log, Event Log, and other database related functions in place. In this post, I'm going to take a look at a few other aspects, not all 100% DotNetNuke based, that should be closely monitored and addressed as well. For those of you that follow me on Twitter, my recent posting about clearing almost 40Gb of rogue data across servers is all part of what lead me to this posting.

Read more...

Comments (1)