New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

DotNetNuke Module Development and the new Web Application Projects

This issue is making me a little crazy (I know a personal problem :).

I see a lot of posts from developers who are hoping the new Web Application Projects will solve a perceived problem with the current dynamic compilation model.

Under the current dynamic compilation model, a DotNetNuke module resides in 2 directories:

  • The Web User Controls and their associated code behind files reside in the "DesktopModules" directory
  • All other code (Data Access Layer and Business Logic Layer code) resides in the "App_Code" directory.

To create a DotNetNuke module, you create a folder in the "DesktopModules" directory for your module and one in the "App-Code" directory.

Then you simply right-click on the folder and "Add New Item.."

Create a class file or a web user control...

And then start writing code. Click save and re-fresh your web browser to see the results.

The reason I am advocating this method is that for beginners, they don't have to learn a complicated Visual Studio configuration, nor do they have to learn how to use additional external programs.

The reason I am advocating this method for advanced developers is because it is extremely fast to develop this way.

In my current tutorial I use the DotNetNuke module templates and then replace a lot of code so the simplicity of the development process may have gotten lost in the 8 page tutorial.

In the latest tutorial that will be released when DotNetNuke 4.1 is released, I will show how to use the method described above and the tutorial is only 4 pages.

Now a lot of current developers use the CodeSmith templates to create the large amount of code needed for the Data Access layer. With the DAL+ coming in the next version (4.1) there will be a 60% reduction of code so you may not need the templates anymore.

Also, working with the Source code version of DotnetNuke can be painfully slow. My recommendation is to not use it. I use the DotNetNuke Starter kit to develop my modules. This compiles fast and is easy to set-up.

I hope that current Dotnetnuke developers will let go of the methods they currently use and see the incredible gains in productivity that VS2005 offers.

  • Use dynamic compilation to improve development speed and to reduce configuration.
  • Use Generics and ObjectDataSources to reduce code and implement pure OO design.
  • Use the new DAL+ to further reduce code by an ADDITINAL 60%+

The only thing the new Web Application Projects provides is the ability to compile your DotNetNuke module into one assembly rather than multiple assemblies. Why is this so important when you still have to distribute a dozen or so files that consist of your web user controls and resource files?

I am confidant the beginning developers will accept these easy to learn and fast to use methods. I just hope the current DotNetNuke developers will see the advantages also.


Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out