Hi,

When we want to show another control (ascx) within a module, I use the following call:

Response.Redirect(DotNetNuke.Common.Globals.NavigateURL("DETAILS", "mid=" + this.ModuleId), false);

Where "DETAILS" is the control key and mid is module id. Currently we want to put a comments module under all screens. So most of my code that makes the above call navigates to a new page but other modules (such as comments module at the bottom of the screen) I placed originally in page are gone (not visible).

What is the correct way of navigating to a different control within a page without affecting other modules placed in the page?

The same issue is been posted by other user:
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/146447/scope/posts/Default.aspx

Anyone please guide on this issue.

Thanks, srikanth.

Hi,

Thanks for showing some interest.

After several hours of research, I found out that there are couple of workarounds:

a) By modifying the skin, so that there is a separate pane (other than the default left, top, right, content, bottom) - By placing our modules into this pane, even if we go to edit mode, the other modules placed in the page will not disappear. But this is a less favourable solution unless you have total control over the design and installation of DotNetNuke-based application.

b) To use ASP.NET Multiview control - we can place multiple user controls and manage them. This sometimes could get very complex and unmaintainable - unless we coin some design pattern and follow that strictly.

I personally use the dynamic control load method (this way you only have one View user control).  Michael Washington discusses the options you have to do this on one of his excellent tutorials here http://adefwebserver.com/DotNetNukeHELP/Misc/ModuleNavigationOptions.htm#Dynamically_Loaded_Controls.

A more detailed example of dynamically loaded controls is here: http://opensource.indyneinc.com/home/DevX/Articles/DynamicLoadUserControlsinDotNetNuke3/tabid/67/Default.aspx.  This is the code I used for my solution.  The only modification I made is that I don't like to use URL parameters to pass values, I instead use session variables (looks cleaner, a little more secure IMO).  And I don't need the "Utility.vb" component.

Carlos