DNN Notes

Tool for checking DNS entries

info@mydnn.org — Sat, 29 Dec 2007 02:02:42 GMT

My favorite tool for checking DNS entries recently created a subscription model for their site. This is their right, of course, but I don't use their tool frequently enough to justify a subscription. Looking for a good replacement, I ran across intoDNS which runs an excellent free DNS check. I thought I'd link to them here in thanks.

I also like

What is a DNS check? If you own a domain name (such as mydnn.org) then you need to make sure that your visitors can find your web server from the name. Part of the Internet is to have Domain Name Servers (DNS) which make that connection for you. A DNS check will make sure that your settings are correct and will function properly.

Some other tools I took a look at:

MyDNN TimeZones Pro 1.2.3 released

info@mydnn.org — Thu, 21 Jun 2007 00:55:00 GMT

I've released a new version of the MyDNN TimeZones Pro module (v 1.2.3). Integrated SWObject to get rid of the annoying box 'Click to activate' on each of the clocks. Added new clocks Swoop, Quartz, and Digital with Date. Moved style sheets into module.css and now each clock has two classes ClockTZ and ClockTZ897 (module number). This allows for cascading styles to be applied (styles were previously emmitted inline and couldn't be overridden).

Generating DNN4 Modules

info@mydnn.org — Sun, 29 Apr 2007 17:16:00 GMT

I started coding DotNetNuke modules back in DNN 1.06 when you had to compile your module into the main source of the project. So much of a DNN module will be the same from one module to the next that a code-generation tool makes a lot of sense. I'd rather tweak and improve my base code in a template so that any best practice techniques can be automatically incorporated into my next module. I won't say that creating a DNN module from scratch by hand is overwhelming--it certainly can be done, but the layers that have been added in DNN 2 & DNN 3 added functionality at the expense of additional code layers.

For DNN3, there are some great solutions:

AppTheory's ATGen SDK (brainchild of DNN Core Team member and Trustee Bryan Andrews and Chris Paterra )
Visual Studio 2003 Templates from DNN Trustee Vicenç Masanas (also lists CodeSmith templates)
Bo Nørgaard's DAL Builder

Some other solutions (ok, but a step behind the generators above):

Nate Thornton's DNN Templates look like they build upon Ashish Agrawal's additions to Mark (lunchin) Hall's earlier templates (Dave Allen-Williams--Dave A-W--fits into this chain somewhere too).
John (grandOPUS) Thomas has VB.Net templates, and MyGeneration also includes standard DNN templates in their install.
Todd Davis' Private Assembly Creation Tool (PACT)

I've use all of the above tools to generate DotNetNuke modules. By far the best tool listed above is AppTheory's ATGen SDK. This tool not only creates the module code, SQL Install, and DNN Manifest file, it also creates a NAnt build script which will package your module in both PA and Source .zip files which include the module name and version number! The files that it creates are very thorough and generate view and edit controls that support localization already. I love this tool, but it hasn't been maintained. For DNN modules targeting DNN 3.x, I would still heartily recommend this solution (warts and all). ATGen SDK will also generate a custom profile provider object for you if you so desire.

All the other solutions (to one extent or another) generate your module source code. Some of the better ones create a Visual Studio project/solution file and a DNN Manifest file (.dnn file). Some of them generate the SQL you'll need to install your tables. Some of them create the DAL code to query your database table and turn the data into business objects for you.

The problem? Where are the solutions for generating module code for DNN4?

The DotNetNuke team ships a module generator that plugs into Visual Studio 2005. It is called a Starter Kit and generates a project that you can use to build your module. It makes a complete 'do nothing' module that is a fine starting point. However, it doesn't target the database table you've created or help you with any code specific to the layout of your module. It creates the files and sets up the namespace. That's fine--I'll not look a gift horse in the mouth, but it is a pale reflection of what could be done for DNN3.

The Starter Kit also only generates VB.Net code. I've written modules in both C# and VB.Net, and I've found that I often have some outside reason for using one language or the other (like porting some existing code from another project of mine to DNN). I'd prefer to have an option of the language that I can use.

So what have I found?

I have found a couple of useful starting points for DNN 4 module creation.

Quizical (ICode) has a set instructions and CodeSmith templates for DNN4.
6Team (French DNN) CodeSmith templates for DNN4.
BiteTheBullet.co.uk has a nice article and port of the Starter Kit to C#

So far, the Quizical's solution seems to be the best. It doesn't create a project/solution file but it does create the SQL table creation scripts and some reasonable VB.Net starter code which is more specific than the Starter Kit initial files.

Has anyone used DNN KickStart (a module generator on Snowcovered)?

Have you seen another DNN 4 module generator that I should look at?

If so, leave a comment!

Problems Upgrading to DNN 4?

info@mydnn.org — Thu, 29 Mar 2007 03:32:00 GMT

Recently I took several DNN installs from DNN 3.2 to DNN 4. I ran into two issues after completing the installs that are worth a mention:

Users were unable to use the core Documents module to download files
Uploading files or installing modules broke

Fortunately, both of these issues are easy to solve.

The first error is caused by a change in how permissions are handled for accessing files in the portals/0/ directory (or whichever directory represents the current portal). Previous to DNN 4.4 access to these directories was available to any user, any role. In DNN 4.4 the File Manager page now gives control to the portal administrator to allow 'View Folder' (Read) and 'Write to Folder' (Upload) permissions to any role for any directory. Checking the box next to All Users for 'View Folder' allowed my files to now be downloaded as before. One interesting symptom of this change is that the you can add a document to the Documents module as Admin, but users of the site won't see anything listed at all. They won't get an Access Denied error when they try to download, the download item won't appear at all!

The second issue presents itself with an error such as the one below:

Failure:

ExceptionSystem.IO.FileNotFoundException: Could not load file or assembly 'SharpZipLib, Version=0.81.0.1407, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. File name: 'SharpZipLib, Version=0.81.0.1407, Culture=neutral, PublicKeyToken=null' at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.ReadZipStream() at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.Install() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

The issue is that DotNetNuke 4.4 now incorporates compression into the core. Great! Unfortunately, if you were already running Blowery compression on your site, there are now two .dll's in your /bin directory with the same code (which is what the error above is trying very hard to tell you, but not doing a very good job). The solution is simple, just delete the Blowery* and ICSharpLib* in the directory (blowery.Web.HttpCompress.dll, blowery.Web.HttpCompress.xml, ICSharpCode.SharpZipLib.dll & ICSharpCode.SharpZipLib.dll in my setup).

New TimeZones Pro Release (1.2)

info@mydnn.org — Thu, 01 Mar 2007 01:42:00 GMT

MyDNN.org released a new version of MyDNN TimeZones Pro on Feburary 28th, 2007. The new release adds functionality for time zones which do not fall on an hour boundary (like India's +5:30 or Australia's +8:45) and Australia's Lord Howe Island (DST +0:30)). The version 1.2 release also includes numerous bug fixes and small enhancements.

Be aware of the change in when the US moves to Daylight Saving Time. Congress changed the date to March 11th through November 4th for 2007 (Energy Policy Act of 2005). Both version 1.1.2 and 1.2.0 (newly released) recognize this change in the date.

Find it at SnowCovered or DotNetNuke Marketplace.

DotNetNuke Module Review Passed!

info@mydnn.org — Fri, 25 Aug 2006 18:29:00 GMT

The MyDNN TimeZones module has passed the DotNetnuke Module Review! This review tests installation and other proper operation to ensure a consistent standard and to encourage the use of best practices. I'm proud to display the Module Review logo for my module.

A Walkthrough the TimeZones module for the DNN Module Review process

info@mydnn.org — Wed, 26 Jul 2006 23:47:00 GMT

I thought I might take you through my thought process as I prepare my module for review. Having published standards (even before a module is reviewed) is helpful so that even module developers who don't opt for a review can still know what constitutes a solid module. I've highlighted some words in purple to indicate steps I'll have to take to make my module work. Some of the requirements are italicized. The module I'm talking about is the MyDNN TimeZones module (a for-pay module).

Taking a look at the required elements I installed the TimeZones module (version 1.1.0) on a clean DNN 3.3.3 installation. The module installed fine using an object qualifier of DNN333 (I didn't test database owner or virtual portals, but both should be fine--it is being used on MyDNN.org on a virtual portal). The uninstall left the /DesktopModules/TimeZones/AdminModules/ folder intact. This could be handled through an instruction to delete the folders in the Uninstall section of the user guide if needed. Globalization should not be a problem as no date or language dependencies should exist. The EULA will need to be assembled to correctly identify the rights of the user.

For Elective Requirements, I offer the module with source as a separate package. This will satisfy the item for #1b if I add an appropriate EULA. Item #1a is supported through the Snowcovered help desk feature although my documentation should be updated to reference this support approach.

For the documentation elective requirement, I should add a section on installation and uninstallation. A reference to the EULA or a reprint of it should be included in the documentation. A separate .pdf file for the documentation in the .zip file appears to be appropriate. I link to the the modules documentation in the sales literature to allow a user to better understand the module before purchase.

For the optional requirements, I support localization in the areas of the module that I've modified recently but not on the first screen I developed. Strings that are displayed in two of the controls can be localized and one is fixed. ISearchable and IPortable are not supported. The TimeZones module works well in a medium trust environment as it only needs DB access and mainstream ASP.Net functions. With regards to portal styles, the output of the module doesn't use portal styles (it has a module.css) but the edit controls should be use the same styles as the core modules.

Some questions:

How should I remove the folder that remains after I uninstall? Why didn't the uninstall remove it?
Does DNN have an example module EULA? What about one that gives appropriate permissions to distribute with a source-code distribution (allows third-party modification, etc.)?

This post seems a little self-aggrandizing, but I hope it is helpful to someone. I was surprised that I won't have to do much to the module to make it meet the standards (in my point of view, at least). I think the module review program is great. It helps module authors by setting a reasonable, attainable standard. Users of DNN will have a selection modules with proven quality. Hopefully the fee will be an enticement for reviewers to get compensation for their effort.

Tim

MyDNN

Beta Testing period for TimeZones Pro!

info@mydnn.org — Fri, 14 Apr 2006 18:25:00 GMT

If you are interseted in beta testing the TimeZones Pro module, please use the Feedback page to send me a note with the subject TimeZones Pro Beta Request.

Thanks!

What calendar module to use?

info@mydnn.org — Fri, 24 Feb 2006 00:57:00 GMT

Have you struggled trying to find a good calendar module? Is the built-in Events module too weak? Well there are a number of modules to choose from and some recent developments that lay a nice path forward.

The DNN Events module hasn't changed much from the DNN 1 version which was a simple port from the IBuySpy sample.

Alan Vance put together AVCalendar as a free alternative to the Events module in DNN 2. This module introduced recurring events and multiple views of the same calendar information. Master calendars allowed several calendars to be consolidated into one 'master' calendar to prevent redundant entry of data. Unfortunately AVanced Systems didn't update the module with the same energy for DNN 3. Eventually a port of the DNN 2 module for DNN 3 came out, but it the energy behind it was diminished. Don't get me wrong here, I really liked the module and have no rights to complain about someone volunteering their time. It began to seem that AVCalendar wouldn't be a good long-term calendar solution--a big disappointment as it is a great module.

The Huston DotNetNuke User Group took over some support for this module, giving it a 'Foster Home.' Intellisoft got involved with Intellisoft Calendar which added AJAX support to show event details without a postback and taking the code a step further.

Fortunately, in addition to these great alternatives, Alan Vance is back in the game, and as a DNN Project team member, no less! AVCalendar is being rolled into the DNN suite of modules as a replacement to the Events module. Taking the name of the current DNN Events (blog) module, it will allow both Event module users and AVCalendar module users to upgrade (forums, download).

I've also had good luck with Enterprise Events from DNNWorx.com.

What calendar module do you like?
What feature would you like to see added?
Post a comment and let me know!

Adding compression to your DotNetNuke site

info@mydnn.org — Tue, 24 Jan 2006 03:14:00 GMT

Today I upgraded a DotNetNuke installation and added compression (soon I'll get around to updating this install, too!). Server-side compression will tell the web server to try to send compressed data to the web browser instead of the full HTML text of each page. This can be quite a savings with DotNetNuke as there are several stylesheets and javascripts to download in addition to a rather large page payload (enhanced with viewstate at the bottom). Fortunately, text (HTML, CSS, and Javascript in this case) all compress nicely, usually between 50% and 80%.

To enable compression on your DotNetNuke site (DNN3.2.2 in my case) you have to make one change to your /bin folder and three changes to your web.config.

First, download the Blowery HTTPCompression module (pick the Version 6, binary only version). Blowery stands for Ben Lowery--a nice guy who has generously donated something valuable to the asp.net community--read his blog. Upload the following files to your DotNetNuke /bin directory on your server:

ICSharpCode.SharpZipLib.xml
ICSharpCode.SharpZipLib.dll
blowery.Web.HttpCompress.xml
blowery.Web.HttpCompress.dll

Mr. Lowery has a very generous license for using this code--just don't claim that it is yours and give credit when possible. So, if you've downloaded the .zip and uploaded the 4 files do your DNN install, you've got the first part of this licked!

Now, you need to make three changes to your web.config. First, add the following XML to the top part of your web.config file. Find </sectionGroup> and add these three lines immediately following:

    <sectionGroup name="blowery.web">
      <section name="httpCompress" type="blowery.Web.HttpCompress.SectionHandler, blowery.Web.HttpCompress"/>
    </sectionGroup>

Next, find the </httpModules> section (it is inside the system.web tag). Insert the following line before the </httpModules>:

Finally, add this section right after </system.web> in my config it is just before <memberrolesprototype>:
<blowery.web>
<httpCompress preferredAlgorithm="gzip" compressionLevel="high">
    <excludedMimeTypes>
      <add type="image/png" />
      <add type="image/jpeg" />
      <add type="image/gif" />
      <add type="application/zip" />
      <add type="application/x-zip-compressed" />
      <add type="application/x-gzip-compressed" />
      <add type="application/x-compressed" />
      <add type="application/octet-stream" />
      <add type="application/pdf" />
    </excludedMimeTypes>
    <excludedPaths>
      <add path="Install/" />
    </excludedPaths>
</httpCompress>
</blowery.web>

Save your web.config file to your site and browse to your home page. After DNN loads the new files, you should notice that each page loads faster than before.

One note of caution before I'm done, please disable (comment or remove) the httpmodule (the <add name="...) before performing an upgrade/update. Compression and the upgrade process do not work well together, although uploading new modules does seem to work fine.

Enjoy!