One of the things that has been bubbling away at the back of my thoughts for a while now is ‘DotNetNuke needs an API’.  Of course, DNN already has loads of API, what I mean by this is an open, extendable, web-service style API.  Lots of times I come across something I need to do, and I immediately think – ‘now this is where an API would be handy’.  So, with a concrete project that I needed to do that really was best done with an API, I turned thoughts into code, and the result is a very early stage DNN Web service API.

I spent a whole cache of hours yesterday tracking down a bug reported with the iFinity Friendly Url Provider. This bug was that the RSS feed button which is in-built into DNN modules didn’t work. The problem turned out to be the same old thing that causes the majority of incompatibility between my Friendly Url Provider and other DNN Core functions and DNN Modules – misuse or non-use of the Friendly Url Provider API. So, please, if anyone writes DNN code for anything, please see what I have to say

With IIS7 starting to make inroads into the installed DNN base, I've fielded a few questions about IIS7 compatibility and my existing work with DotNetNuke friendly Urls.  I know things are going to change in the future with the upcoming DNN 5 release and (probably) taking advantage of native IIS7 features.  Here's my outlook on what we might expect.