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

HomeHomeDevelopment and...Development and...Getting StartedGetting StartedOne Module ... Or Many?One Module ... Or Many?
Previous
 
Next
New Post
5/31/2013 1:06 AM
 

I have an implementation that could be done in a number of small modules, or perhaps as one or two large modules.

The benefit of using smaller modules is that I can arrange them on my page as I want. But a single monolithic module would have a single codebase, and since I'm using JQuery and JQueryUI a bit, I assume it would also work quicker.

What's the general preference when developing a number of small-but-related modules? Monolithic, or not?

(For info, these modules would be scoped by user id for the most part.)

Dylan.

 
New Post
5/31/2013 5:58 PM
 
If you put the smaller modules in one large Visual Studio solution (as a compiled module, or Web Application Project), it would still be one code base, and you could still put as many modules on pages as you like. In other words.. if you are creating a compiled module, it really doesnt matter what you choose..

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
6/1/2013 12:57 AM
 

OK, that is sage advice. I'll put my modules together in the same solution.

One follow-up question, then, if my modules all access the same set of database tables, should I have a module just for the database objects to be installed in? Like a "controller" module?

I am worried that I may be complicating things by having multiple modules each with a bit of the table structure in them.

Dylan.

 
New Post
6/2/2013 2:01 AM
 
Technically you could have 1 controller that accesses everything. I general though, you would have 1 controller per table, that usually makes for code that is better readable.Remember that this is one big solution, so you can access common code (ie. your business layer) from all the modules.

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedOne Module ... Or Many?One Module ... Or Many?


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