Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Is both ItemID and ModuleID mandatory on the table designIs both ItemID and ModuleID mandatory on the table design
Previous
 
Next
New Post
5/11/2006 6:35 PM
 

Hi there. I am sorry if this has been asked before but i could not find it on any forumn

I created a module and just to be on the safe side, I added ItemID, ModuleID, CreateByUser and CreatedDate as Columns to my table and then went ahead and generated the Info, Controller, SQLDataprovider and Dataprovider with the modified SeaburyDesign CodeSmith templates as shown on the videos.

Fair enough, i had to make some Namespace adjustments, but then i ran into a problem on the ViewXXX.ascx.vb class. The PageLoad method is asking for

colImageLinkBannerss = objImageLinkBannerss.GetImageLinkBanners(ModuleId)

However, the autogenerated GetImageLinkBanners method that signature is.

Public MustOverride Function GetImageLinkBanners(ByVal itemID As Integer, ByVal moduleId As Integer) As IDataReader

The problem now is that the ItemID is unavailable at the PageLoad method. Commenting this out will only solve the problem in the short run.

 
New Post
5/12/2006 4:30 AM
 
Hello

PortalID, ModuleID and ItemID columns all depend on your module design. You will naturally have an itemID - this is the unique ID per record, but whether you want your data displayed at module level or portal level is up to you.

For example - when you add an HTML/Textbox, each version of the module has unique text, hence this is stored at module level and would need a moduleID. In my Events module though, each module you add looks at the central repsoitory of information, so I hinge it off PortalID, if you see what I mean.

I always add CreatedByUserID, ChangedByUserID, CreatedDate and ChangedDate to ALL my tables for auditing purposes.


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
5/12/2006 8:27 AM
 

An important element in delevoping module is understanding the scope of the data.  In all but a few instances your data should be keyed off of the PortalID.  What this means, is that if you look at the relationships for your table, can you ultimately resolve the PortalID associated with your data.  This is important because DotNetNuke uses a virtual portal model which allows multiple independent portals to run from a single installation.  Does this mean you need to store PortalID in your table?  No.  It means you need to have a relation to some data that ultimately has a relation with PortalID.  So if you store ModuleID or TabID with your data then you can use those pieces to get to the PortalID since a module or tab is related to a single portal.


Joe Brinkman
DNN Corp.
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Is both ItemID and ModuleID mandatory on the table designIs both ItemID and ModuleID mandatory on the table design


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out