A few months ago I released V4 of my DNN Development templates, which included a new project template for Themes (skins). This weekend I was working on a new theme (skin) for a customer project and came across a few changes I needed/wanted to make to the Theme project template, so you get to benefit from those changes as I have put a new release out of the project templates.

I have released version 2.2 of my open source DotNetNuke Module Development Templates. Version 2.2 is really just a minor update for the release, with a couple of fixes, one big, and the rest fairly small.

This blog post is no longer being maintained, visit the Christoc.com Tutorial for customizing the module development templates.

With the 2.0 release of my module development project templates last week I’ve had a few inquiries into how to customize the templates. You can download the templates from https://christoctemplate.codeplex.com/

Why Modify the Templates?

First, why might you want to modify the custom templates? The main reason is that these templates are defined using a specific namespace, DotNetNuke.Modules.*, which is fine in most cases, but what if you want to use your own namespace? Well you have to create a project, then search/replace all instances of that namespace, while not removing any DNN references at the same time. Customizing the project templates will allow you to define your own company namespace, email address, website, and even copyright information, in the template so that you do not have to search/replace every time you create a new project.

With the release of DotNetNuke 7.0 (and now the more recent 7.0.2), it was time to update my module development project templates. If you have worked with my module development templates before, here are the major changes for this release. If you haven’t worked with them before please read this whole blog post as I discuss how to get up and running with the templates.