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.0multiple asp pages in single modulemultiple asp pages in single module
Previous
 
Next
New Post
11/9/2007 3:24 AM
 

Hi all,

I need to develop an application that holds a menu, multiple (>10) grids, multiple wizards, edit screens, insert/add screens, settings screens, etc, etc. I am looking at how best to do this within DNN and I'm not sure I can find a sattisfactory solution.

The idea of having each of these "screens" in a single module is just to much, simply managing the uploads/updates of all the different modules is enough to keep me from going there. I am currently looking around for ways to develop an "application" in a single DNN module, but that seems quite hard to do as well.

I am still fairly new to ASP, coming from PHP and others, and I just found out it is not possible to dynamically include ASP files, so that kind of got me off the idea of doing it in a single module.

I've read about some ways to simulate it, but it doesnt sound too safe and you cant use too complex ASP files I believe.

I do see different DNN modules however that are quite complex and seem to be built up out of various ASP pages. Are there any documents on this, tutorials, any experts or people that have experience in doing something similar?

I have been through the forum a bit and found some posts that were close to what I wanted, however the solution was not fitting for me.

To try and describe a bit more what I want for the application: there will be a menu on the left hand side, fixed, controlling the entire app, the right hand side is then reserved for whichever item is active or clicked, clicking the menu will reload the page, holding the menu on the left but showing a different "page" on the right hand side, etc, etc. quite simple, yet with a lot of different "pages".

Thanks in advance for any help.

Regards,

Adriaan

 
New Post
11/9/2007 3:57 AM
 

Adriaan,

What you're looking for can certainly be done. Actually it can be done several ways (ain't that always the case...)

First of all I think you need to start thinking of your pages as Controls. Your own application-menu could also be thought of as a control of course. You will need to decide wether you will:

  • leave loading of the right control to DNN (by using the controlkey and adding several View-controls to your module) or
  • take control of this yourself by using some sort of dispatcher on your main view control that will dynamically load the controls (kind-of the DNN does this itself.

Personally I used both directions but prefer the latter to stay in control myself.

Does this get you anywhere?


Web applications, DNN websites, modules, skins and support
 
New Post
11/9/2007 7:03 PM
 

There are a number of different ways you could proceeded.

But it seems to me - the first thing you need to get your head around is how DNN works.

FIrstly, the menu - the functionality you are talking about in terms of a menu is pretty standard fare in DNN.

Your menu could be embedded as a part of the SKIN design for your site. 

THe DNNMENU or SOLPART menu skin control can automatically do what you are looking for here.
And dnn with dynamically handle the generation of your menu and runtime - this is not something you
need to code for - just put the MENU control on your skin with some config settings and stylesheet info
and DNN will do the rest for you automatically.

Secondly, site structure,  the first thing to understand about DNN is that there are actually no ASP web pages
anywhere in the DNN system.

DNN in based around a set of WEB CONTROLS that are all dynamically loaded at RUNTIME onto one somewhat complex
default.aspx web page.

The look and feel of this default.aspx web page is control by a SKIN.ascx web control and a set of .css style sheets.

The defualt.aspx web page loads the SKIN.ascx control dynamically at runtime - and then the controls defined in the SKIN.ascx file
are used to load the current page based on the setting of a TABID querystring value.

All this is handled automatically for you by DNN.

WESTA

 

 
New Post
11/21/2007 1:51 AM
 

Hi guys,

Thanks for both responses so far. After I made that post I continued looking around a bit for options and I ran into both options Stefan mentioned. The idea of seeing my "pages" as controls is clear to me now and that is the way to go for me.

I have looked briefly into the multiple view controls for DNN, but couldn't get that to work and couldn't find a nice (small) example I could download and try out.

I ran into some problems with the loading of the controls and viewstate, but the web is filled with pages on that so I was able to work that out okay. So far, all seems to be going well and I can continue with my development.

If one of you has a nice working example of the DNN multiple view controls, or if one of you is able to explain to me how to use that in a few lines, please do so, as I would still like to know how to use this feature.

Again, thanks for your responses and at the moment I'm going with loading the controls dynamically.

Regards,

Adriaan

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0multiple asp pages in single modulemultiple asp pages in single module


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