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.0Module Development - Multiple ASCX filesModule Development - Multiple ASCX files
Previous
 
Next
New Post
1/12/2007 8:00 AM
 

Hi there,

I am missing so real basic knowledge on module development but cant seem to find the solution...

I can happily create simple modules using thre Starter Kits which by default have 'View' 'Edit' and 'Settings' ascx which is fine for simple modules.

But what about modules that require workflow or different ascxs to be used?

How do I get my module to load its default ascx (View) and then when actions are completed load another ascx from the same module?

All the examples and tutorials I have found all use examples that only use one ascx for rendering output. None seem to show how to develop modules that use multiple ascx...

Any help greatly appreciated....thanks in advance

Geoff

 
New Post
1/12/2007 10:00 AM
 
Geoff - take a look at the forums module which has multiple ".ascx" files. Note the syntax in the *.dnn file (this is the bootstrap installer file for any DNN module). You can easily create a module with multiple ascx files and tie them to each other. Let me know if you need any additional help.

AcuitiDP - Oracle Data Provider for DotNetNuke
 
New Post
1/12/2007 5:09 PM
 
GeoffHall wrote

Hi there,

I am missing so real basic knowledge on module development but cant seem to find the solution...

I can happily create simple modules using thre Starter Kits which by default have 'View' 'Edit' and 'Settings' ascx which is fine for simple modules.

But what about modules that require workflow or different ascxs to be used?

How do I get my module to load its default ascx (View) and then when actions are completed load another ascx from the same module?

All the examples and tutorials I have found all use examples that only use one ascx for rendering output. None seem to show how to develop modules that use multiple ascx...

Any help greatly appreciated....thanks in advance

Geoff

 

I learned how to do this by studying the ManageUsers.ascx file used for user registration / user creation / user maintenance; which does a decend job of ussing different ascx controls to provide virtual pages.  The entire process of creating my own user sign in module (www.SkydiveSecure.org) proved to be extremely educational, afterwards I went back and changed some of the previous modules I had developed to incorporated some of the tricks I learned.

 
New Post
1/12/2007 5:12 PM
 

Geoff...

Do a search in the forum and you'll see this question has been posed many times.  I've experienced issues with multiple views with ASP2.0 that I still haven't gotten a good answer to. Developement works with ASP1.1, but I've recently started to convert to ASP2.0 and problems have been arising.

Check out this forum link:

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/111/threadid/95670/scope/posts/Default.aspx

 
New Post
1/13/2007 9:39 AM
 
GeoffHall wrote

But what about modules that require workflow or different ascxs to be used?

How do I get my module to load its default ascx (View) and then when actions are completed load another ascx from the same module?

All the examples and tutorials I have found all use examples that only use one ascx for rendering output. None seem to show how to develop modules that use multiple ascx...

If you just want to make a link from one .ascx control to another see this tutorial:

NavigateURL: How to make a link (VB &C#)

The only disadvantage is that when the user navigates to the other .ascx control, any other module on the page disappears. Many times this is ok because you want the user to concentrate on the decision you may need them to make at that time. When they navigate back to the main .ascx control everything will appear as normal.

For those situations where this is not the desired behavior I suggest looking at the Blog module. This module simply gives each function it's own .ascx control that loads at the same time. Instead of navigating to each .ascx control, they are all on the page at the same time. This allows the portal administrator the ability to indicate the layout and allows them to better integrate the module into their site.

(For example I always place the list of blogs on the left hand side and the blogs themselves on the right hand side. I also delete the "search for a blog" control.)

Also look at the FotoVision module (demo). It uses a menu on the left and hides the rest of the controls and only shows them when you click on an item on the menu.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Development - Multiple ASCX filesModule Development - Multiple ASCX files


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