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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Inheritance of DNN ModulesInheritance of DNN Modules
Previous
 
Next
New Post
9/19/2009 1:19 PM
 

Hi,

Can one DNN module inherit another DNN module? Does DNN recommend doing so?

 

 
New Post
9/19/2009 1:34 PM
 

 You definitely can.

I don't know if I would recommend for or against it however. 

The dangers would be that if the original module gets deleted your module may break.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
9/20/2009 12:24 AM
 

Thx a lot for your reply.

Further to this, I would like to know how to put it in place

E.g I have a parent DNN module (say a grid module) with structure that has View, Edit and Settings page along with the Components folder which includes the DAL layer. I have provided filtering / sorting and all basic features to this. As per the various business scenario's I want to reutilize the same functionality but with additional features. How can I do it by inheriting this parent module? I want to inherit this into 2 more child modules which have additional functionality like for e.g.:

1. Grid which has cells with backcolor based on the data displayed in it

2. Grid data displayed in pivot

Just like we have the base class PortalModuleBase, or IModuleCommunicator can I have something like GenericGridBase?

 

 
New Post
9/20/2009 5:01 AM
 

Have GenericGridBase inherit from PortalModuleBase, then (say) ColoredGrid inherits from GenericGridBase.

It's hard to say if this is a great design without being much closer to what you actually want to do.


Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
9/21/2009 7:10 AM
 
The basic purpose of having this kind of inheritance is core functionalities associated with the master grid remain intact (like filtering / sorting / css etc). Whenever a new business requirement of adding up something more to the existing grid comes, I need not touch the existing grid code. I should simply be able to inherit this base grid and continue with the new functionality that needs to be developed over and above it.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Inheritance of DNN ModulesInheritance of DNN Modules


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