Archive
Monthly
Go
|
|
DNN Blog
By Charles Nurse on
3/30/2012
This blog has been cross-posted from my personal blog.
 DotNetNuke has a rich eco-system of Modules, both Open Source and Commercial. In many ways this is our biggest strength as a CMS platform. No matter what you want to do with your site – there is often a module that already does it.
In my opinion this is due to the flexibility provided by the core DotNetNuke Framework. Many other platforms are very prescriptive – as an extension developer you have to follow a fixed shopping list of rules – there is invariably only one way to create an extension, which may not work for what you want to do.
|
By Chris Hammond on
5/25/2011 5:21 PM
If you haven’t checked out the DotNetNuke Video Library lately, you really should, there is a lot of great content in there. I just uploaded 5 new videos as part of a new series that I am recording.
Beginning DotNetNuke Module Development, creating a Task Manager module for DNN. This will be a series of videos that get created over the next couple of months revolving around the creation of an open source Task Manager module. The module will be part of the DotNetNuke Forge, and the source code will be hosted on Codeplex.com. ...
|
By Chris Hammond on
2/22/2011 8:46 PM
If you have any interest in doing DotNetNuke Module Development you should check out the Module Development Webinar that starts next Tuesday. The class runs from Tuesday the 1st through Friday the 4th, and runs 8am-12pm Pacific Time the first three days, the 4th day runs from 8am-10am. Here’s a brief description of the webinar Module Development in DotNetNuke is the primary delivery mechanism of extended functionality...
|
By Chris Hammond on
1/4/2011 7:49 PM
Late last year I created a blog post and video about a new version of the module development template that I released on Codeplex. This new template uses MSBuild scripts instead of NANT scripts to automate the packaging process for the modules built with the template. The MSBuild script works well out of the box, to package your module you simple change into RELEASE mode and then execute the build. If your project contains references to DLLs (in the website’s BIN folder) that you also need to package up so that you can deploy them with the module however things become a little murky. Earlier today Bruce posted on that original blog post asking how to include those DLLs in the build script so they get packaged automagically.
|
By Chris Hammond on
6/3/2010 3:53 PM
Two days ago I posted a blog about configuring a DotNetNuke development environment, in preparation for today’s blog post about a C# module development template that I recently released on Codeplex. So today’s blog post is about how to utilize the template, customizing the VSTemplate file to fit your needs with company name, namespace, email, and URL. Installing the template, and then creating a quick and easy module using the template.
If you haven’t read my post about setting up your development environment I encourage you to do so before proceeding, as the steps I’m going to walk you through below assume you are running a similar environment to me. The following assumes you are using DotNetNuke V5+ and Visual Studio 2008, if you are using an older version of DNN and Visual Studio there are no guarantees that this template will do anything for you except cause pain. It’s time to upgrade folks! DNN 5 rocks!
Tags: Development,C#;Module,Module Development,DNN,Visual Studio 2008
|
|