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 StartedUsing same ascx for View and EditUsing same ascx for View and Edit
Previous
 
Next
New Post
1/4/2011 7:01 PM
 
Hi All,
I'm developing a module which will list a set of records in a grid, and allow the user to view or edit records from here. So far so standard.

However, being lazy and wanting to avoid coding two almost identical ascx'sI want to use the same ascx for the View and Edit of the records - just disabling the appropriate controls when in View mode.

In a non-DNN world, I'd use an ascx with a 'mode' property which I set to view or edit and then code it to enable disable as appropriate. Is this possible with a DNN module control?

As I type this I'm thinking that perhaps the solution is to have my common control as a nested ascx which is placed on my View.ascx and Edit.ascx. The View.ascx sets the embedded control's mode to 'view' and the Edit sets the mode to 'edit'.

Is this the best approach, or is there a better one which is supported by DNN?

Regards,

James
 
New Post
1/5/2011 10:24 AM
 
Either of those approaches is usable in DotNetNuke although it will be up to your code to properly check that the logged in user is properly authorized to edit the module's data.

Another approach that I like to use as it avoids the switch to the edit skin and isolation of the active module alone on the page is to have one dispatch module control (ascx usercontrol inheriting from PortalModuleBase) that then uses LoadControl to load the appropriate child controls for various views, editing, etc. Although these child controls do not have to inherit from PortalModuleBase, it is much easier to do so as you can make use of DotNetNuke's localization features, etch. by passing the dispatch control's module configuration, etc. to the child control.

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
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedUsing same ascx for View and EditUsing same ascx for View and Edit


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