Day of DotNetNuke Recap

This weekend was the Day of DotNetNuke in Charlotte, NC.  I was there to present two session, along with three other Engage colleagues (Oliver Hine and Anthony Overkamp also presented).  I was honored to be able to present on the Client Resource Management Framework and the Services Framework, two newer components in DotNetNuke (introduced in DNN 6.1 and 6.2, respectively).

Making Full Use of the Client Resource Management Framework

The slides are available to view at http://bdukes.github.com/Making-Full-Use-of-the-Client-Resource-Management-Framework/.  This is a really exciting opportunity for skin and module developers to dramatically improve the performance of their components by letting DotNetNuke worry about managing our client resource (CSS and JavaScript) for us.  The big takeaways here are to use the framework, and make sure you turn it on, if you’re a site administrator.

Designing a Mobile-Enabling API

New in the just-released DotNetNuke 6.2 is the Services Framework.  This gives module developers a great way to create web APIs to allow accessing the modules’ data in new and exciting ways.  This opens up new development models and new flexibility in 3rd party extension, as well as opening up the way to make your components easier to consume from a native smartphone application.  The slides from this one can be viewed at http://bdukes.github.com/Designing-a-Mobile-Enabling-API/, and the example projects are in the repository (https://github.com/bdukes/Designing-a-Mobile-Enabling-API) as well.

Thanks to those who attended my sessions and the conference in general, it was a really well-designed day and great to see everyone who came.  If you have any questions about my sessions (whether you attended or not), feel free to contact me via this blog or on twitter.