Last week I started a DNN/ASP.NET hybrid experiment. I've worked with DNN in the past, and overall you get quick, easy, CMS solutions, but it feels a bit cookie cutter. The way the modules are placed into the site often feels really static and "cheap." The payoff, though, is that you get the support of literally thousands of developers at http://www.snowcovered.comthat all code to the same CMS, meaning you get lots and lots of out-of-the-boxfunctionality for aCMS or social website.
What I'm experimenting with now is whether or not I can mix and match ASP.NET directly with DNN. Using a simple Control Wrapper module, which takes any given ASCX control and wraps it in a DNN module so you can insert it into a DNN page, I'm making entire controls for the new 1.FM that are essentiallythe "meat" of all the 1.FM pages. That means I can still have my own custom admin pages and custom controls without having to code directly for DNN, but when I find an out-of-the-box module that I want to use, such as a forum, image gallery, reporting engine, chat room, or anything else, I can immediatley make sure of them.
So far, everything seems to be going smoothly. I am planning on writing an article on the process once it's done, and I'll post another blog entry when I have my findings, so stay tuned.
If this works, it could bring on a whole new way for developers to build websites. No longer will you have to be a DNN Developer to take full advantage of the DNN infrastructure and supporting features.
To be continued.
-eli