.NET Answers

Many of you won’t care too much about creating Portal Specific Modules because you’ll be creating modules for an environment that only has one portal. However, if you are creating a module for resell, or you will be using the module in a multi-portal environment, you’ll need this next piece of information I’m going to give you.

In fact, I should have given you this information when I told you how to set up your databases. Sorry.

Each module instance will have its own module ID. What this means to you as a developer is that your top-level table(s) need to have a ModuleId field (integer) that can be filled with the module ID the data should be associated with.

This will allow you to install the module multiple times on your site or on multiple portals without having the data conflicting with the other instances or other modules.

You might also want to put the PortalId in all of your tables so that it is easy to remove data when a table is removed. Or you might want to implement a cascading delete. That part of the implementation is totally up to you.

The important point is that you need to have some way of associating the data in your database with the portal it should display in. Adding the ModuleID field is how you do this.

Thanks to Charles Nurse for his help with this topic

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

Related Post

• DotNetNuke Modules - Finding The Page a Module is On
• DotNetNuke Modules - Exceptions the DNN Way
• DotNetNuke Modules - Making Content Portable