RJ Dudley

Snowcovered is the single best source of DotNetNuke modules.  I've used a number of DNN modules over the past several years, all purchased from Snowcovered.  Given the head start of Snowcovered, I never understood the point of the DNN marketplace, but this move seems very intelligent.

DotNetNuke Corp. is pleased to announce the acquisition of Snowcovered. Snowcovered has done a tremendous job building a market for DotNetNuke modules and skins which has empowered DotNetNuke software ISVs and helped grow the DotNetNuke ecosystem. DotNetNuke Corp. has been the steward for the DotNetNuke open source project and helped drive the growth of the platform and ecosystem. Bringing the two companies together will continue the growth of the DotNetNuke ecosystem by creating closer ties between the platform and the large, rich library of third party modules and skins.

We will operate Snowcovered in the same positive, beneficial manner the DotNetNuke community has come to expect. Brice Snow, founder of Snowcovered, will continue as a full-time participant in the business as we merge the two organizations. The DotNetNuke commercial ecosystem will benefit from a closer integration of the DotNetNuke platform with the commercial marketplace where users can purchase the modules and skins they need for success.

Full story at http://www.dotnetnuke.com/DotNetNukeAcquisitionFAQs/tabid/1352/Default.aspx

For a recent client's project, I needed a good looking DotNetNuke skin.  After searching through Snowcovered, I cam across the DotNetNuke skins by DNN Covered.  These skins are amazingly beautiful!  We purchased one, uploaded it, and it worked perfectly.  It's perfect for our site.

Not only are their skins beautiful and affordable, they have great customer support.  The skin page said the PSD files were included in the package, but they were not present in the download.  I put in a help ticket before going to sleep, and when I woke up the next morning, I had a reply with the PSD files from DNN Covered.

DNN Covered definitely has the feel for how DotNetNuke works, and a feel for the DNN community.  Thanks DNN Covered!

CleanTown USA is Pittsburgh’s favorite car wash.  It’s an amazing 16,000 sq ft facility, with two giant conveyor belts that move your car as a team cleans the interior.

The first website was a highly stylized design that provided a retro-futuristic feel, but took forever to load, and the navigation was not very user friendly.  It was also a pain to update, since every page was created by slicing apart Photoshop files and touching up the HTML in Dreamweaver.

To provide greater functionality, better navigation and quicker load times, we decided to use DotNetNuke as the basis for the new website.  The included calendar, photo gallery and blog functionality are nice additions to the site.  Gift card sales are enabled by CATALooK .netStore Pro, and custom information forms are handled by XMod.  We compromised on the design to provide layout flexibility, and the default blue skin fit the company perfectly.

You can see the upgraded site at www.CleanTownUSA.com.

When users register, the profile page asks for a Unit, right above the Street.  A better label would be "Apt/Unit", since this is the place to put in an apartment number.  You can't change this label in the Manage Profile Properties, so you need to do a little editing.

There are at least 4 places you can change this text, but the only one that affects the public view of a user's profile is ~/admin/Users/App_LocalResources\Profile.ascx.resx.  Edit this file in a text editor, find "Unit:" and change it to "Apt/Unit:", then save it.  Your registration and profile pages will now show the new label.

The label in the Manage Profile Properties won't change (and I haven't found that edit yet), but your registration and user's Manage Profile pages will all show this change.

I'm finishing up a DotNetNuke site, and am using CATALooK.netStore Pro for the first time.  I've used a number of shopping carts in my days--PDG Cart, LaGarde Storefront and Candypress come immediately to mind, but there are a couple whose names escape me now.  I was pleasantly surprised to find that CATALooK is one of the better carts I've used.  It it packed with features, and handles configurable products better than any other cart I've used.

Once you have your DotNetNuke site, installation is fairly easy.  Ignore the install.htm file; instead, use the admin guide in the documentation folder.  It's written much better, and illustrated with screenshots.  CATALooK installs a number of modules.  Some are public modules, some are admin only.  Some can go on the same page, but some must go on separate pages.  There is an extremely helpful table in the admin guide to sort this all out.

Once you get the pages created and modules installed, it's time to configure the cart.  One of the limitations of DotNetNuke is that multi-page forms just don't happen.  Ths is often simulated by changing the visibility of different panels on a page.  This works fine for simple user interface forms, but the administrative pages are a different story.  Some of them are long, and look very intimidating.  After you set up one or two products, you'll learn to ignore the sections you don't need, and the setup is much easier.  I strongly suggest running through the example of a configurable product in the admin guide before you set up any of your own products--it's very helpful and takes only a short time.  In addition to a very advanced component relationship ability, simple text attributes are supported, and are pretty flexible.

The look of the public modules is somewhat controlled by module settings.  For most cases, this is all that is required for the look to be "good enough".  Without the source code, you have some ability to change the layouts and hide elements.  User displays are comprised of a number of controls, some of which can't be hidden, but removing them from the page will cause errors.  For complete control of the design, you'll need to purchase the package with source code and do some editing.  Modules can be skinned, and a couple are included in the package.  A few more are available from Snowcovered.

Importantly, CATALooK has the ability to swith the sensitive pages into SSL mode (you need to buy an SSL separately) if that's required  CATALooK integrates with a number of payment gateways, as well as .netCharge, so an SSL isn't always required.  The feature list is extensive, but some of the major ones include referral tracking, product import, coupons and discounts.  Language packes are available for several languages.  Follow the link below for the full list.

So where does CATALooK fall short, IMHO?  I think there are a couple of shortcomings, but nothing that can't be fixed in an upcoming minor release.  However, if any of these points are deal-vreakers for you, you may want to contact the developers to make sure they're on the radar screen.

1. The "Your Cart" graphic is terrible.  I think it's a magnifying glass looking at your cart, but it looks like a blob eating a shopping cart.
2. If you use Text Options for your product, when the user chooses an option, a postback is triggered, and it's not very noticeable.  If the user clicks the "add to cart" button quick enough, they won't notice anything, and the item will be added to the cart.  If they sit still for the duration of the postback, they'll see the product price get updated.  If they wait just long enough to click the add to cart button, they'll get a message that there are no items in their cart.  I'd like to see this updated to something AJAX-y so there's no postback.
3. You need to use Public registration, since a user account is created automatically.  A random user name and password is assigned if the user leaves them blank, or if you hide them on the checkout form.  You can't use Private registration at all.  If you use Verified, your user will have to receive their e-mail and log in between the billing and shipping information forms.  Ideally, there would not be a login required so Verified could still be used, but allow users to complete the checkout without logging in.
4. Once the checkout is complete, redirect to a non-SSL secured page.
5. Although pages are secure by SSL, the links to images or included files on these pages are not rewritten, so your user gets a "Show insecure items" warning.
6. You can create custom shipping rules, but there is no option to use only the custom rules.  They must be used with some other service.  Although the admin guide says the custom rules are checked first, I still received an error that USPS could not be contacted.

Nothing truly serious, but can be confusing or annoying to the end user.

If you're looking for a shopping cart for a DotNetNuke website, check out CataLook at http://www.snowcovered.com/Snowcovered2/Default.aspx?tabid=242&PackageID=3445&r=bf37884a72.  I've been pleased with my experience.

WebIS has released FlexMail 2007, a replacement for the Pocket Outlook which ships on Windows Mobile 5.0 devices.  This is a significant upgrade to the FlexMail 2006, which I've used for several months now on my Treo 700w, but found myself wishing for a few more features and faster performance.  My few wishes and then some seem to have been taken care of in this new release.

FlexMail is far and above better in how it displayes messages with HTML formatting, and handles IMAP accounts better than Pocket Outlook.  GMail POP3 SSL is supported, as is storing messages on an SD card.  The featurelist is long, and everyone likes different things, so just go check it out for yourself.

Full story at http://webis.net/products_info.php?p_id=mail.

The nomination period ends September 1, so get on this soon if you haven't already.

Last week Packt Publishing announced an Open Source Content Management System contest. The contest is designed to encourage, support, recognize and reward Open Source Content Management Systems and offers a top prize of US$5000 to the winning project, second prize $3000, and third prize $2000.

Full story at http://dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1053/Default.aspx

After working with XMod for about an hour and a half last night, I’m of the opinion that 90% of the modules available on Snowcovered.com can pack their bags and go home.  The 90 minutes is rougly the time from purchase, through installation, to finishing my first working form.

Installation isn’t difficult, but you do need to read the installation guide.  There are several PAs for different versions of DNN.  After you upload the correct PA, you need to do a little manual configuration (easy, and well guided in the installation instructions).

Lats night’s task was to build an input form for a client’s site.  This is one of several forms my client needs, and is the shortest.  The complete documentation is 370 pages, but the vast majority is reference and examples.  The Getting Started is about 10 pages, and was all I needed for last night’s task.  It’s intimidating when you first see the size of the documentation, but it doesn’t take long to get rolling.

Creating the forms is a snap—there’s a simple editor for beginners.  All you do is select the type of input you want, and a little properties box shows up.  You enter some information about that input, and add the field.  You can change the input’s characteristics manually in the editor as well, and trak your progress with the handy preview.  You even have complete control over how the confirmation e-mails look, if you need those.

The authors claim XMod “Can’t do everything, but you may never notice”, and they’re not kidding.  I’ll have a longer review when I get this site finished.  But my first look is very positive.

Bil Simser responded to Shaun Walker's DNN vs. Sharepoint Feature Matrix, and for some reason I can't get the Submit button to work on Bil's blog.  So I'm posting my comments here.  Two points to add to Bil's great list:

1) Unless there have been some changes made, storing files in the file system with DNN is not secure.  This is the only way to store files in DNN 3 (unless the newest release changes this), and one option in DNN 4.  Someone paying attention can access files by direct URL.  In SharePoint, files are stored in the database, and acceses to these files can be strinctly controlled at several levels.

2) It's actually far, far easier to develop and deploy SP webparts with the free SmartPart than it is to develop DNN PAs.  The distribution method of PAs is great, but development of DNN modules can be a pain.  The SmartPart allows any ASCX control to be used in SharePoint, and has found significant use in my SP installations.  Without the SmartPart, developing for either can be a miserable experience.

I was asked the other day if I knew of a DNN document library with version control.  At the time, I didn't, but I've since found one from WillowTree Software.

This is a DNN 3.1.x or later version of the Wrox Document Dontrol (DNN ported) module. This was first offered by Mark Hoskins (KodHeaz), then Robert J Collins (WillowTree Software), then Tam Tran Minh (TTT Company), and lastly (and once again) Robert J Collins (WillowTree Software).

In Mindsharp's SharePoint Discussions group, the following question was posted:

Does anyone have experience with both SharePoint and DotNetNuke to the point where they could comment on the benefits of each are compared to the other?  Is there a type of installation where you might use one vs. the other?

Here's the answer I posted in the group:

SP and DNN are very different beasts which offer some similar functionalities.  I'm using SP as a generic term for either WSS or SPS, which is a different decision.  DNN is really an easy website creation tool, while SP was designed to be an information repository and collaboration tool in a corporate environment.  The best way to summarize might be "Extranet vs. Intranet".  My thinking is Extranet=DNN, Intranet=SP.  DNN is designed to be used and maintained by persons with little IT experience.  SP is one of those things that will require having a decent IT person around.

First question would be whether or not you need tight integration with Office.  If so, then hands down your only choice is SP.  Another feature that DNN is lacking is a document library with version control, although one may appear down the road.  SP offers full-text indexing of the documents you store in it, and so you can search inside the documents in its libraries.  DNN doesn't offer this.  SP stores its documents very securely in the SQL database; DNN stores them as files, which means if someone knows the right path, the site's security could be bypassed and the documents downloaded directly.

If you don't need the tight Office integration, DNN is a very valid choice for a website.  A good use would be for a school's website.  DNN supports multiple child portals, just as SP does, and you can distribute administration, just as with SP.  The school could have its main portal, and each department or club could have its own child portal, each with their own radically different looks.  True, you could pull off the school's website with SP, but it wouldn't be so flexible, and you would put in a lot more effort to make it work.

Another consideration is what type of authentication you need to use.  WSS was designed to integrate with Active Directory, DNN was designed to work with anonymous users and Forms Authentication.  There are ways to make DNN work with AD, and WSS work with anonymous users, but anytime you make a change as significant as authentication scheme, you introduce adminsitrative overhead.  One point of using these tools is to simplyify your life, not create extra work.

Cost might also be a consideration.  True, if you have Windows 2K3, then WSS is essentially free; DNN is entirely free.  There are a lot of good web parts available for free and cheap for WSS, but many are very expensive.  DNN can also be extended with inexpensive or free modules, and even the ones you have to pay for are still pretty cheap.

One main difference I see is the amount of different things you can do with DNN.  DNN can also serve as an e-commerce platform, or host robust photo galleries (rather than the "list of photos" in SP).  There are some nice calendar modules for DNN that not only list events, but allow registrations and can accept payment for them.  In this case, it might seem like SP is lacking in some functionality, but SP was never designed to do these things--these are functions of a website, not a collaboration tool.

Skinning is a bazillion times easier with DNN.  The DNN core team did a great job with its skinning engine, and there are lots of skins available for free or cheap.  Changing the look of a single page, or entire portal is done with a simple package upload and a few mouse clicks.  With enough work, you can do some really nice skinning on SP (both SPS and WSS), but it takes some work.  I've done both, and DNN is by far easier and more powerful (mainly due to DNN's simplicity--features which are hidden or difficult really aren't features at all).

DNN runs very well in a shared hosting environment; SP, not so much.  Although DNN only ships with SQL Server provider, if you're handy enough, you would write one for MySQL, or Vista, etc.  You don't have that option with SP--it's SQL Server only.

<update 2006-02-01>

If you didn't come here from there, Bil Simser has a much more detailed post at http://weblogs.asp.net/bsimser/archive/2006/01/31/437023.aspx.  Bil also includes some of the features of SharePoint 'v-Next' (currently due to be released at the end of this year), and better breakdown of the OOTB functionalities.

spreskit

dnnbooks

Want one, too?  Become a benefactor: http://www.dotnetnuke.com/Home/tabid/894/Default.aspx.

The logo is actually grey (matches my eyes), it just looks blue-ish with the flash.

Now playing: Chamber Music Society of Lincoln Center - 3. Allegro Assai (Brandenburg Concerto #2 In F, BWV 1047)

It's been three years since the release of DotNetNuke, and today Shaun announced the DotNetNuke Benefactor Program.  Basically, you can make a donation to support the project, and get some extra benefits in return.  DNN will remain open source and free, and becoming a benefactor is optional.

The DotNetNuke Benefactor Program was created with the intent to preserve the delicate balance between the needs of the open source community, the serious business ecosystem it has fostered, and the on-going management of the project. The Benefactor Program provides the ability for community members to gain access to a premium set of layered benefit packages; with each level designed to satisfy the needs of a specific stakeholder group.

Full information at http://www.dotnetnuke.com/Home/tabid/894/Default.aspx.

Now playing: Pearl Jam - You've Got to Hide Your Love Away

Way cool, Eric!

This is the first in a series of articles showing how to integrate a Crystal Report Manager into DotNetNuke. This article will step through creating a private assembly using Visual Studio as the development environment and using the Data Access Layer in DNN.

Full article at http://aspalliance.com/733

I've had the priviledge of reading Dan Egan's Building Websites with VB.NET and DotNetNuke 3.0 recently, and there are other reviews out there, I figured I'd chime in also.

Overall, I think this is a better book for the DNN beginner than the WROX book (see http://www.rjdudley.com/blog/ReviewProfessionalDotNetNukeASPNETPortals.aspx), and is more suitable to the non-technical people who may be administrating the portal, but not developing for it.  It's not perfect, but I think these users will appreciate some of the extra work Dan put into this book.  Most of the book is written as if you are building a coffehouse locator together, so much of the book flows from one topic into another, and is written with a point.

Chapter 1 starts you with an overview of portals in general, and explains why DNN is a very good choice.  Dan also lays the groundwork for the portal you'll be building (Coffe Connections), and demonstrates a technique called "user stories" than can help design an effective portal.

Chapter 2 covers installation on a local machine, which I think many users may not need to worry about.  It's not something everyone needs to know, but it's a good idea to familiarize oneself with the information even if you won't be performing the installation.

Chapter 3 really gets into the meat of DotNetNuke.  It's probably the best coverage of users, roles and pages and how they operate in DotNetNuke I've seen.  There is a chunk of very technical information regarding the Membership Provider; if you're not developing for DNN, you can safely ignore this section and not miss anything.  Useful information for all in this chapter includes how to control user registration, how to create pages and control access to them using user roles.  This chapter is written using the user stories created in chapter 1.

Chapter 4 is great.  This chapter covers all the standard modules included with DotNetNuke, with a simple explanation.  Coffee Connections isn't tied into this chapter too tightly, but it fits.  Dan went above the usual descriptions of the modules, and includes some "Practical Purposes" of each module, and how to administrate the modules.  This is a very useful chapter for anyone who will be working with DNN.

Chapter 5 covers the host and admin tools.  This seems a little out of order, but contains great information on how to administer your portal.  It covers the difference between 'host' and 'admin' logins, how to change site settings, upload new images to be used on the site, view logs and a few other features.

Chapters 6 and 7 get way off course in the context of building Coffee Connections.  They contain some very detailed technical information, more suitable for the developer than administrator.  The non-technical administrator can skip over these chapters and not miss too much.  For the developer, chapter 6 covers caching, config files, providers and other detailed information you'll need to develop custom modules.  Chapter 7 is an introduction into building custom modules (called "Private Assemblies") in DNN.  Included are discussions of setup and adding the proper user controls (you need at least 3 ASCX files--a View, an Edit, and a Settings), packaging your module and adding it to a site, and creating a business logic layer and a data access layer using the database provider module.  Extensive code examples in VB.NET are provided.  The sample module you're building is a custom Coffee Shop Listing control for Coffee Connections.  This chapter alone is nearly 1/5 of the book's almost 300 pages, and is very detailed.

Chapter 8 covers creating DNN skins and containers, and how to apply them to your site.  You create Coffee Connections' skin using Visual Studio, and ending up with an HTML and token based skin.  This is a short chapter, and doesn't go too deep into skinning (but compared to custom modules, skinning isn't a deep subject anyway), but you'll be able to create DNN skins after reading this chapter.

Chapter 9 lists some must-have modules, where to find them and how to use them.  Another great chapter, and I now use several modules I didn't know about until I read this chapter.

Chapter 10 covers deploying your portal to a live site, using FTP and SQL Server Enterprise Manager.  Presumably, many readers will already have passed this point, but it's good for the beginner ready to go live.

Chapter 11 covers one of DNN's best features--supporting multiple portals from a single installation.  This is exceptionally useful for a school or other setup where one parent portal may be the gateway to the portals of other departments, etc.

Chapter 12 covers the Provider Model as its implemented in DNN.  If you're new to the provider model, DNN is a very complicated example to try and learn from.  Chapter 12 will bring you up to speed with the theory of the provider model so you'll be able to work with DNN's implementation effectively.

Overall, I think this book is better for the non-technical user than WROX's book, but adds technical information in a few spots that can distract such a user.  If you're a hard core DNN developer, DNN's book is probably the better technical manual (being written by the DNN Core Team, you'd expect that), but this book makes an excellent secondary reference.