This video blog series gives an introduction to DotNetNuke module development. It assumes a basic knowledge of .NET website development in either VB.NET or C#. I did these videos a few months ago, so the DNN version is a little behind, but going forward, I intend to post more relevant content.
Part 1 - Prerequisites and DotNetNuke Installation
You should have the following software to do module development in DotNetNuke:
- Visual Studio 2008, 2010, or 2012 (preferably Professional edition of higher to allow for remote debugging)
- SQL Server 2008 - free edition is fine
- WebMatrix/IIS Express - free
- DotNetNuke Community Edition Install - whatever edition you would like to minimally support
Part 2 - Starting the Module
Download and install the VS Template, create a new VS project for our project using the template, and install the empty project in DNN to register the module.
Download and install the template
Get the Christoc module development template for Visual Studio. You may need to install the MSBuild tasks first.
Create the project for our module
Use a good naming convention for your project, namespace, and dll. Example that most vendors use are: CompanyName.ModuleName. Look at Coding Staff for example. They have a product called tabbox. Their dll is: CodingStaff.TabBox.dll and their code folder in DesktopModules is CodingStaff.TabBox. I imaging their namespaces are something like: CodingStaff.Module.TabBox.Components, etc... Remember, building in Release mode is what invokes the packaging via the MSBuild scripts. The packaging output files into the source folder/packages.
Register module in DNN
After we build the install package, we open DNN and use the install package to register our module definitions in DNN so we can put the module on a page and begin our cycle of coding and testing. Remember to use the *source* installation package for our module because our source folder in /DesktopModules will get overwritten with our package.
Part 3 - Coding and Testing
I will provide a more in-depth look at using Entity Framework as a data layer in your DNN modules.
Part 4 - Caching and Debugging
See the Related files section below to download a zipped copy of the project.