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...DNN Platform (o...DNN Platform (o...Best Design Practices Question for Custom ModulesBest Design Practices Question for Custom Modules
Previous
 
Next
New Post
7/14/2009 10:49 AM
 

My company is working on a project that is using DNN as its foundation. We are moving along fine with module creation (using ASP.NET 3.5), and I understand the method of module installation; I've created a few and installed them just fine.

What I am not clear on is what the proper way is to install and use modules with multiple controls, and how to control page flow between these multiple controls.

Here's my example - I have a form (on its own ASCX control) that is intended to collect meta information on lists that a user can save. So basically the form consists of fields to collect first name, last name, etc. and when the form is submitted, a record is saved and I get back the id of this new list. 

Now, a user can add items to this list, and this is where I get lost. It would make much more sense to me to create a separate ASCX file for viewing and editing lists, but a number of people have suggested that I keep this functionality ON THE SAME ASCX as the one I save form information on, and hide/show panels depending on the requested operation. 

This is counter-intuitive to me, and I foresee a maintenance headache later on, so what do I have to do to create these multiple files and ensure that they are properly navigated to?

Thanks for your help/feedback. 

 
New Post
7/14/2009 9:04 PM
Accepted Answer 

This tutorial by Michael Washington describes various ways to navigate from one control to another or load a control as a child of another:

http://www.adefwebserver.com/DotNetNukeHELP/Misc/ModuleNavigationOptions.htm

All three techniques are valid ones - each has its benefits and disadvantages. Generally, I create separate controls for view, edit, administrative functions, and settings. However, if there are multiple view controls or a master-detail form relationship I prefer to either dynamically load the child/detail ascx control or use panels or a multi-view control to show/hide parts of a single control. Much of the choice comes down to whether you wish to continue to show other modules on the page and apply the normal page skin when displaying alternate views, edit screens, or details. The standard DNN approach of navigating to a module control by navigating to a url containing the control's ControlKey results in the module being isolated on the page and a switch to the admin skin.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
7/15/2009 8:38 AM
 

William:

This is EXACTLY what I was looking for (and I've searched high and low). Grateful for your information and input. Thanks!

 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Best Design Practices Question for Custom ModulesBest Design Practices Question for Custom 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