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.0Developing "large" modules?Developing "large" modules?
Previous
 
Next
New Post
2/18/2007 5:46 PM
 
Thanks everyone for the replies.  Sorry I didn't get back sooner.  So from what I'm reading it appears that I'd have to develop a number of modules that I'd then arrange in the portal to facilitate the viewing and editing of the reviews.  No biggie.  I believe that I have some of the legwork done already in my original implementation and I'm hoping it's a quick port to the DNN framework.  But before I bite off way more than I can chew I think I'm going to try a few smaller projects before I develop something that will take months to complete.  Between work and the family life I get a handful of hours each week to toy around with this stuff.
 
New Post
2/18/2007 6:17 PM
 

Howard:

I have found myself in the position you are in right now.  But in my case the applications were (notice I said applications and not modules) were complex enough to warrant the development of a custom module from scratch.  I based my solution in the Indyneinc.com sample you mention with the exception that I decided to maintain state (ie: what module to load) in session variables instead of passing them as query string variables (cleaner, a little more secure).  I also decided to have just one View module even though the application consists of several user controls to be loaded dynamically.  By the way, I did the data access using the DAL+ following Michael's great tutorials.

Depending on how complex your ideas are for the module functionality, it may actually be easier to develop your module from scratch.  I attempted to modify a module I purchased with code but it was after all so different, it needed so many changes, plus I needed to learn somebody else's logic, that I dropped it and started from scratch.

Just my .02, others WILL have different opinions but this worked great for me.

Carlos

 

 
New Post
4/11/2007 11:25 AM
 

Hi!!

I am using DNN 4.0.2 since last year. Now, I need to develop a large module. And would like to use the functionality suggested on the previous posts - from indyneinc - As you did.

I did not manage to make the code "Switchboard" to work. Do you think you could share your "already worked" solution with me?

I usually develop in C#. Has anyone made this work in C#?

Thank you all.

Andreia

 
New Post
4/11/2007 5:10 PM
 

nick and all-

 

I do quite a bit of 'large module' developement one thig is that they have many parts that are each 'modules' - i find this no different than developing pages - yes you place modules on individual pages - you could automate that if you really want but if you are building for very specific purposes then its not that hard to have multiple edit and view modes for a module - now myself i dont like to load modules like the indyne sample (if i am thinking of the same one you guys were talking about) I try to plan out all the screens and how they connect - some connect for the users and sometimes those connections happen in the database

 

Overall I think you just need to not think of modules so much as applications --

More of me rambling huh -- need sleep to many app to build this month :)


Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules
 
New Post
4/11/2007 10:45 PM
 

Yes I would agree that moving beyond - Hello World - can at first seem daunting inside a Modular enviroment.  And sadly there is not as much documentation on this aspect as there is on the more general elements on the system.

But I also feel that to a certain extent the reason for this - is that once you move beyond single action modules to site wide - portal implementations - that there are almost as many ways to move forward as there are sites to develop.

Given your comments above - it is entierly feasible however that you could build the whole review engine in a single module.  With the actual layout controlled at runtime thru querystrings - and maybe some form of skinning if you want variable layouts for each category.

default.aspx?tabid=50&cat=1  - select a category
default.aspx?tabid=50&cat=1&review=23  - select a review

With the "enter a review" also handled inside the module:
default.aspx?tabid=50&cat=1&new=true  - create a new review

The module uses the querystring info to turn on the appropriate Panels of Info for display at runtime.  In this way the majority of your module is self contained.

Admin tasks such as Editing / Moderating / Deleting reviews can also be handled inside the module - by simply turning on ADMIN related buttons if the users has the right permissions - this could also include INLINE editing as well if you so desire.

Westa

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Developing "large" modules?Developing "large" 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