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.0To extend DNN am I stuck creating modules?To extend DNN am I stuck creating modules?
Previous
 
Next
New Post
10/25/2006 7:43 PM
 

Yes, you can integrate ASPX pages, but a lot of DNN features it is hard to get the UI to match (I deleted stuff I posted previsouly becuase I was mixed up).

I have found a compromise between developing full blown DNN modules and your own ASPX pages. See http://www.opendnn.com/nbspnbspnbspnbspOpenSmartModule/Features/tabid/96/Default.aspx. This is a standard DNN module (so everything in DNN keeps working) and it hosts generic ASP.NET user controls (ASCX files), so you can quickly make ASCX files and have them hosted by a real DNN module. It may be the best of both approaches.


WildVoice.com Michael Levy - Are you ready to be heard? WildVoice.com
 
New Post
10/25/2006 8:21 PM
 

Actually, let me clarify something. Yes, you can integrate your own aspx pages. A good example is in DNN itself. See RSS.aspx. I've actually done this in a number of situations. The trick is to Inherit from Framework.PageBase and make sure the your siteurls.config rules don't interfere with your request. Within these pages you can access intrinsic DNN objects (my comment before were true for ASMX files becuase Url rewriter explictly checks for ASPX and AXD extensions - I belive). In our system we have a number of ASPX pages like this, but they are mostly used for small pop-up windows and requests that don't generate a UI (like RSS generation).

If you want to make these file share the look and feel as the rest of your portal, then you have some issues. Look at the implementation of default.aspx and see how skins and modules are injected. To get matching look is tough, especially in a shared portal environment.

I still think OpenSmartModule is a nice solution for quick development that doesn't require a custom module but still needs to integrate into DNN.


WildVoice.com Michael Levy - Are you ready to be heard? WildVoice.com
 
New Post
10/25/2006 8:58 PM
 
What I'd actually like to be able to do is reuse work that is done in DNN in a 'standard' ASP.NET 2.0 website. 

My initial thought was write my stuff in ASPX (or non-DNN ascx), but take advantage of consistency, look/feel, and security and eventually be able to also leverage these in a non-DNN website.  However, from your reply it seems no one has considered this.

Let's entertain the thought of writing DNN modules.  Can the modules (essentially user controls) be developed in a manner so they can be leveraged in non-DNN sites?  Could it be structured as follows?

DNN Module class hierarchy:

DNN.WebControl.{module class}
|
My.WebControl.WebPart (housed in MyDNNSite.dll)
|
ActualUserControlClass (housed in MyDNNSite.dll)



Class hierarchy for user control (or webpart) on non-DNN site:

System.Web.UI.UserControl (or WebPart)
|
My.WebControl.WebPart (my custom class [non-dnn] housed in MyNonDNNSite.dll)
|
ActualUserControlClass (housed in MyNonDNNSite.dll)



If I did not use any DNN-specific logic for my 'ActualUserControlClass' in the DNN site, could I move that to my non-DNN site?


 
New Post
10/26/2006 7:04 AM
 

Yes, if you create a core User Control as an ASCX that does not use any DNN specific functionality, you can use this ASCX as a component in a DNN module and in other sites.

Think of OpenSmartModule as a generic DNN Module that simply hosts ASCX User controls within DNN.


WildVoice.com Michael Levy - Are you ready to be heard? WildVoice.com
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0To extend DNN am I stuck creating modules?To extend DNN am I stuck creating 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