I’m frequently asked about the DNN Corp development process. The “great debate” started when interviewing for the job of SVP Engineering as I was asked: “How familiar are you with Agile Scrum”? “Do you subscribe to Waterfall?” “What do you think of Kanban?” You’d be surprised how much interviewers focused on these sorts of questions rather than the results I had overseen. Sheesh!

Seems not that long ago that we released 6.0 with its new UI and infrastructural switch to C#. Even more recently, in November, we added Mobile support to the platform in the form of 6.1, and have been incrementally enhancing 6.1 each month. This culminated in the 6.1.5 release made on Wednesday, April 4th, in which we changed to using the 51 Degrees.mobi device detection and database. Besides bringing benefits to Professional and Enterprise Edition customers, our CE customers now have Device Detection Management and Site Redirection Management built-in. 

But the real story today is 6.2...

It was brought to my attention that, while a number of people read and liked my initial blog entry, that they didn't know who I was. So...

I can’t believe that I’m at this fine company, working with such wonderful people, for four months, and only now writing my first blog! Bad Bob!! That behavior will have to change right away.

Let’s begin with some first impressions…

On Friday, March 16th, we released an updated CTP version of the new DotNetNuke Services Framework. This is truly exciting!

For developers who are experienced with the DotNetNuke APIs, they may not care much. On the other hand, if they're wanting to expose module services externally in a standardized way, then the Service Framework and coming Service Layer API's will be a major boon. Indeed, we're taking that approach with some of our own modules in DotNetNuke v6.2, examples being messaging, the new journal, and notifications.