Mark Hoskins

Before there were Web parts, DotNetNuke created installable private assemblies nicknamed modules to encapsulate the functionality desired within a modular environment. It doesn't take much experience developing modules for DotNetNuke before you start asking the age-old questions: I know that it's powerful, but where do I start? I know this is handled in DNN, but how? How do I structure the module and create the installable package? At this point you are most likely starting to think instinctively about how to utilize a combination of existing tools and reusable code or templates to streamline development time. In the DotNetNuke community, one of the most commonly asked questions is how to integrate CodeSmith or MyGeneration templates to create the Data Abstraction Laye... (more)