Comments on: The Seven Sins of DotNetNuke Module Developers http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/ Nik Kalyani's Irrationally Exuberant Musings on Technology Tue, 31 Aug 2010 00:46:00 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Dnnguy http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-71 Dnnguy Wed, 26 May 2010 06:10:29 +0000 http://kalyani.com/?p=1093#comment-71 I would say this apply to normal asp .net application except one or two point, it is not specifically for DNN. I would say this apply to normal asp .net application except one or two point, it is not specifically for DNN.

]]> By: Adrian http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-68 Adrian Wed, 28 Apr 2010 04:04:31 +0000 http://kalyani.com/?p=1093#comment-68 Excellent post. I plan to forward this to my web developer who is not necessarily one to commit such sins, but has inherited some code that most definitely has! This would serve as a good "heads up" to any outsourced developers I may use also, as the start of a specification document ...<br><br>I now look forward to reading the Sins of DNN Skin Designers, which lands fairly and squarely in my lap Excellent post. I plan to forward this to my web developer who is not necessarily one to commit such sins, but has inherited some code that most definitely has! This would serve as a good “heads up” to any outsourced developers I may use also, as the start of a specification document …

I now look forward to reading the Sins of DNN Skin Designers, which lands fairly and squarely in my lap

]]> By: Aderson Oliveira http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-65 Aderson Oliveira Sat, 24 Apr 2010 02:30:25 +0000 http://kalyani.com/?p=1093#comment-65 I do understand your point of view and I agree. I debated with myself quite a lot before deciding to use DNN for blogging instead of Wordpress. But I did that not because DNN would be the best option for the task in hand, but because it would be a bit strange that I would be posting videos about DNN but using another platform.<br><br>Please don't take it as a criticism. I was just picking on you. :) I do understand your point of view and I agree. I debated with myself quite a lot before deciding to use DNN for blogging instead of WordPress. But I did that not because DNN would be the best option for the task in hand, but because it would be a bit strange that I would be posting videos about DNN but using another platform.

Please don't take it as a criticism. I was just picking on you. :)

]]> By: techbubble http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-64 techbubble Sat, 24 Apr 2010 02:03:47 +0000 http://kalyani.com/?p=1093#comment-64 It's a fair comment. I like to use the most suitable tool for a task with the least bit of overhead. In this case, my only need was for a blog -- I did not need membership, adding other application functionality, enabling others to post content, etc. I evaluated various blog solutions, hosted and on-premise. I wanted something that would run with minimal fuss on Amazon EC2. I settled for WP on-premise as it was quick and easy to setup via the Web Platform Installer and other than a periodic "white screen of death," it has served well. It's a fair comment. I like to use the most suitable tool for a task with the least bit of overhead. In this case, my only need was for a blog — I did not need membership, adding other application functionality, enabling others to post content, etc. I evaluated various blog solutions, hosted and on-premise. I wanted something that would run with minimal fuss on Amazon EC2. I settled for WP on-premise as it was quick and easy to setup via the Web Platform Installer and other than a periodic “white screen of death,” it has served well.

]]> By: Aderson Oliveira http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-63 Aderson Oliveira Sat, 24 Apr 2010 01:50:54 +0000 http://kalyani.com/?p=1093#comment-63 Where, in the realm of DNN sins, would you put "Using Wordpress instead of DotNetNuke for a blog" ;)<br><br>Jokes aside, very good post and I will be seeking redemption from this list from now on. I will use it as a check list for sure Where, in the realm of DNN sins, would you put “Using WordPress instead of DotNetNuke for a blog” ;)

Jokes aside, very good post and I will be seeking redemption from this list from now on. I will use it as a check list for sure

]]> By: Paul Bolejack http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-58 Paul Bolejack Mon, 01 Mar 2010 01:45:47 +0000 http://kalyani.com/?p=1093#comment-58 Thanks. Although there is a lot of information out there to help one learn DNN, there's not much in the way of best practices. This helps pull some of that together.<br><br>With respect to sin #1... the inline width styles coming out of the core admin modules can be really annoying. Thanks. Although there is a lot of information out there to help one learn DNN, there's not much in the way of best practices. This helps pull some of that together.

With respect to sin #1… the inline width styles coming out of the core admin modules can be really annoying.

]]> By: Bruce Chapman http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-57 Bruce Chapman Thu, 25 Feb 2010 03:37:45 +0000 http://kalyani.com/?p=1093#comment-57 This is very important information for module developers out there. I would also add that, while it is tempting to skip over these for 'quick and dirty' applications - quick and dirty applications have a funny tendency of living for a long time, and causing problems down the track from the shortcuts.<br><br>Thankfully I'm (mostly) free of these sins, though at times I've been known to fall into the UpdatePanel trap, only to regret it later on. I have seen some truly shocking implementations of the UpdatePanel though. This is very important information for module developers out there. I would also add that, while it is tempting to skip over these for 'quick and dirty' applications – quick and dirty applications have a funny tendency of living for a long time, and causing problems down the track from the shortcuts.

Thankfully I'm (mostly) free of these sins, though at times I've been known to fall into the UpdatePanel trap, only to regret it later on. I have seen some truly shocking implementations of the UpdatePanel though.

]]> By: Rodney Joyce http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-52 Rodney Joyce Wed, 03 Feb 2010 23:18:36 +0000 http://kalyani.com/?p=1093#comment-52 Great post as always Nik - thanks for sharing... guilty of a few sins myself.. Great post as always Nik – thanks for sharing… guilty of a few sins myself..

]]> By: uberVU - social comments http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-50 uberVU - social comments Sat, 30 Jan 2010 21:41:15 +0000 http://kalyani.com/?p=1093#comment-50 <strong>Social comments and analytics for this post...</strong> This post was mentioned on Twitter by techbubble: Blogged: The Seven Sins of DotNetNuke Module Developers http://bit.ly/9dssxw... Social comments and analytics for this post…

This post was mentioned on Twitter by techbubble: Blogged: The Seven Sins of DotNetNuke Module Developers http://bit.ly/9dssxw...

]]> By: wmorgenweck http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-49 wmorgenweck Sat, 30 Jan 2010 19:39:12 +0000 http://kalyani.com/?p=1093#comment-49 Excellent post Nik. I would have to suggest that there are exceptions to the Custom Settings rule. While the current module settings is a standard, it is far from user friendly. In our latest release of Active Social we introduced a modal window that is opened from the module actions and provides one click, very quick access to our basic module settings. We also make our settings immediately available when you first add the module to the page. In most cases this saves some extra clicks too.<br><br><br>I would say another sin would be including third-party components with the module that aren't packaged properly. Even worse is when the components are not licensed properly. Excellent post Nik. I would have to suggest that there are exceptions to the Custom Settings rule. While the current module settings is a standard, it is far from user friendly. In our latest release of Active Social we introduced a modal window that is opened from the module actions and provides one click, very quick access to our basic module settings. We also make our settings immediately available when you first add the module to the page. In most cases this saves some extra clicks too.

I would say another sin would be including third-party components with the module that aren't packaged properly. Even worse is when the components are not licensed properly.

]]> By: Han http://www.kalyani.com/2010/01/the-seven-sins-of-dotnetnuke-module-developers/comment-page-1/#comment-48 Han Sat, 30 Jan 2010 10:04:17 +0000 http://kalyani.com/?p=1093#comment-48 Very helpful blog! Thanks, Nik. Look forward to the next one. Very helpful blog! Thanks, Nik. Look forward to the next one.

]]>