I am not sure exactly what you are asking, but I will throw my 2 cents in too. There are two basic ways to programatically get around in DNN NavigateURL and EditUrl.

If its an existing Core page or a page from another module then NavigateUrl is the way to go. Pass in your target TabId, controlkey, and parameters as arguments.

If you are creating a custom control and you want to get to another ascx file in your module it would probably be easier to use the EditUrl function. It doesn't require a TabId. Just name the ControlKey you listed in your module definition and pass any parameters you need. For example:

Response.Redirect(EditUrl("ItemId", ItemId.ToString(), "Edit"));

'ItemId' is the Name of the Key that you want passed into the URL and 'ItemId.ToString()' is the value of the ItemId Key, and 'Edit' is the Key name of the control in the module definition

Hope this helps.

also.. if you want to redirect to another tab, it would be better not to use a hard coded tabname, but let the user define to what page and module should be redirected.

You could easily add some module settings, first allowing the user to select the page, next to select the module. You could even just give him the pages that contain modules you can redirect to

DNN Blog | Twitter: @erikvb | LinkedIn:

(@openarrow)

Thats a fine idea. I would be willing to bet that lots of other folks would like to keep other modules present on pages within their own modules. I have a customer that has a dashboard that he wants visible within his module no matter which page he is on. He wants it in his TopPane. I ended up using an AJAX UpdatePanel control to create the illusion of page navigation without an actual postback. Then I placed his dashboard in an update panel and set it to update continuiously.

I like the idea of using the multiview control when displaying external modules. I could have saved myself some trouble.

Cheers!