Today marks another milestone in the upcoming Hadron release of DotNetNuke. For the first time ever, DotNetNuke is offering a Community Technology Preview that will allow you to begin testing the latest version long before we have completed all the features. As I discussed last week, the CTP is not intended to be production ready software but is an opportunity for the community to get a chance to start kicking the tires. The CTP is an important milestone as it will allow us to gather feedback from the community much earlier in the release cycle and thereby allow us more time to incorporate that feedback into the final release.

If you didn’t see Shaun’s blog post earlier this week you should give it a good read through. The post announced the fact that starting with Version 6.0 (targeted for Q2 2011) DotNetNuke will no longer be developed/released as a VB.NET Application. All development of the core platform will be in C# (this does not mean that the community modules for the platform will change languages).

...

So this is the third and final post in the module development series of blogs I started last week. The first two covered

1. Configuring your development environment
2. Customizing and installing a C# module development template

This post is going to tell you how to utilize an open source project called NAnt to package up your modules quickly and easily, so that they can be installed on various DotNetNuke sites. The C# module development template that I released last week comes with a NAnt BUILD script included, so when you create a project using the template (as we do in blog #2) you are ready to use NAnt to package the module, you must get NAnt configure though, so let’s walk through that process.

So this is the first in a series of promised blog posts that I am long overdue on! These posts are a follow up to a Beginning DotNetNuke Module Development webinar that we provided back on May 17th. If you didn’t attend the webinar you missed out, but you do get to benefit from these blog posts if you want to easily get setup and running with C# module development for DotNetNuke.

This first post will be discussing the development environment that I configure when I am doing DotNetNuke module development, in addition to this post I’ve got a post about a free Visual Studio template that I am releasing on Codeplex that makes setting up your first DNN module very easy. As well as another blog post about using NANT to automate the packaging of your DNN modules so that you can easily deploy them to other environments.