Last post Dec 17, 2005 02:37 PM by email@example.com
Dec 16, 2005 11:17 PM|DOMAIN0|LINK
I'm a former ASP programmer, and recently made the move to ASP.NET. I've heard a lot about DNN, so decided to check it out. Over the past few weeks, I've read a LOT of documentation - but I think I'm missing a piece of the puzzle.
Essentially, I understand the necessity (and positives) associated with "Modules", and I understand the ASP.NET language (as well as C#) - but I don't quite know where DNN fits in. It doesn't appear to be an interpreter for modules (since they are written
in either VB or C# - both languages that ASP.NET understands).
I see a lot of docs explaining how to use the preset features of DNN (like managing users, their read/write permissions, inline editing and formatting of content, dynamically adding content, etc...), but what if I don't need that? Do I still need DNN, or
For example, say I have a functioning ASP.NET page (with layout completed, master-pages, themes, etc..), and I find a cool, pre-built DNN Forums module I want to have for the site. Since the module is written in either VB or C#, does DNN still have to act
as intermediary? Can't I just use the Module like any other ASP.NET control? If not - is there any reason why?
Don't get me wrong - DNN looks like it serves a terrific purpose (one I will undoubtedly use on other projects), but it seems like a lot of backend if you only want a single module's functionality, and not the rest of the pre-bundled items.
Like I said - I think I'm missing something critical. Can anyone see what I'm missing? Or if (yikes) I got it right
Dec 17, 2005 02:37 PMfirstname.lastname@example.org|LINK
DNN is a portal framework. It provides a unified environment to develop and deploy the modules, with DNN handling the majority of the work. Modules written for DNN will rely on the DNN framework, so if you intend to use them you need to use DNN. If you
would rather not use DNN, comparable apps exist that you can use in your own developed site.