Importance of Carefully Selecting Your Vendor and Understanding The Development Cycle
Introduction to DNN Custom Module Development
DNN, formerly known as DotNetNuke, has been around for a while. One of its editions, called DotNetNuke Professional Edition, was launched in February 2009, with version 4.9. Four years after that, in July 2013 to be precise, this edition was renamed Evoq Content. Furthermore, the DNN platform is open-source software, which is distributed under an MIT License. With that, it means website owners wouldn't need much technical knowledge before operating their site and adding any functionality that's not available in the DNN core modules.
DNN platform is now becoming popular by the day, not just as a blogging platform but also as a Content Management System (CMS). Many organizations, both small and large, are already making use of the platform for their day-to-day website needs. For you to get the best out of your DNN website, you'll surely need to add more functionalities to it.
While there are several forms of extensibility for the DotNetNuke platforms, the most common one is module development. Speaking of that, it's worth knowing that you can handle the development for DNN modules in several ways, using tools such as Visual Studio 2010 and 2012. Apart from that, you can also make use of WebMatrix and express (free) editions of Visual Studio for the DNN module development.
In this article, I'll be sharing with you some of the best practices for DotNetNuke module development. However, before we go into that, let's have a look at some of the important things that you need to know about DNN modules. In case you're already familiar with "module", you can skip this part and move over to the next section, where we'll be discussing the DotNetNuke module development best practices. But, in the case you're new to DNN and would like to know about DotNetNuke modules, this is for you.