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.0Modules VERSUS Web User ControlsModules VERSUS Web User Controls
Previous
 
Next
New Post
2/23/2006 3:13 PM
 

What is the reasoning behind using Modules versus Web User Controls?  Web User Controls are a lot easier to develop and install.

Please set me straight.

 
New Post
2/24/2006 9:08 AM
 
First off, modules are user controls. Second, in order to support the rich environment that DNN provides, additional properties needed to be there. We could've used interfaces for these properties, but then every developer would've had to implement those interfaces manually, which means tieing into every aspect of DNN. This wouldn't be a fun task and would multiply module development 10 fold, if not more. Using basic user controls just doesn't make sense.

You're more than welcome to develop your modules as user controls as long as you create a module to wrap that (i.e. create a View.ascx module control that has a MyCustomView.ascx control on it). This would be more work for you, but your controls would obviously be more transferrable, if you ever decided to transition away from DNN. That's a decision you really have to make on your own.

Actually, if you think about it, you're lucky. The current version of SharePoint requires you to create server controls (as opposed to user controls). This means no design-time interface. The next version is .NET 2.0, so I'm pretty sure it'll make use of web parts exclusively, which will make things easier. All-in-all, creating modules isn't much harder than creating controls. The only problem is that you can't toss them on any random page to test them - they have to be on a DNN install. This could possibly be fixed, tho. I don't think anyone has really asked for this capability, but I've personally thought about the advantages of it.

We're always open to suggestions, so if you have any, let us know!

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
2/25/2006 12:55 PM
 
Do you see being able to use .Net 2.0 webparts directly in DNN in the future?
 
New Post
2/28/2006 8:08 PM
 
See  Dan Caron's blog -parts 1-9.

Michael Freidgeim http://geekswithblogs.net/mnf
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Modules VERSUS Web User ControlsModules VERSUS Web User Controls


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