If built a custom user control (like the sectionheadcontrol) that contains the EditURL function, the function will return -1 for the ModuleID.


How do I call the EditURL("MyEditControl") in a custom user control that will return the moduleID of the current module instance?

OK, I found something that works but would this be considered a best pratice.

In my custom user control I created a public property called EditURLValue like so

Private _EditURLValue As String

Public Property EditURLValue() As String

Get

Return _EditURLValue

End Get

Set(ByVal Value As String)

_EditURLValue = Value

End Set

End Property

Then I created the custom user control on my main form like so

<cus:MyControl  id="mcMyCustomControl"  runat="server" EditURLValue='<%# EditURL("SomeEditPage") %>'    ></cus:MyControl>


Back at my custom user control (front end form this time)

I created a Hyperlink control and used this for the NavigateURL Property

NavigateURL='<% # EditURLValue() %>'


Now the Hyperlink in the custom user control will return the module ID,  But is there a better way.....

Did anyone ever get a chance to look at this?  

I'm really interested in hearing from folks that have developed large modules and how they kept from having a single .ascx page with 1000 or more lines of html.

Is your UserControl inherit from the PortalModuleBase? In my modules with many sub-controls, I just have to make sure they are Inheriting from the PortalModuleControl and not the UserControl object. This should give you a valid me.ModuleId along with all the other objects DNN creates.

What I usually do, is create a class that inherits from the PortalModuleBase, and I'll use that in my custom modules. This way if the namespace changes again, I just have 1 file to update.

Thanks for the info.  I think this is the piece I was missing.  I should be able to give it a try today.

OK.. the EditURL in the custom user control is still giving me -1 for a moduleid.  Heres what I have:

User Control.ascx.vb

Imports System
Imports System.Web
Imports System.Web.UI

Namespace myns.DNN.Modules.MyCusModuleName

Public MustInherit Class CustomUserControl
Inherits Entities.Modules.PortalModuleBase
...
...
...
End Class
End Namespace

UserControl.ascx

<%@ Control Language="vb" AutoEventWireup="false" Codebehind="UserControl.ascx.vb" Inherits="myns.DNN.Modules.MyCusModuleName.CustomUserControl" %>

<asp:hyperlink id="hypNavEdit" NavigateUrl='<%# EditURL("SomeEditPage") %>' runat="server" > Edit Part Summary</asp:hyperlink>

MAINModuleControl.ascx

<%@ Register TagPrefix="Custom" TagName="ctrl" Src="UserControl.ascx" %>

<Custom:ctrl id="cusctrl1" runat="server"></Custom:ctrl>

I then declared the cusctrl in the MainModuleControl.ascx.vb

Protected WithEvents cusctrl1 As myns.DNN.Modules.MyCusModuleName.CustomUserControl



The custom user control loads, but the ModuleID in the hyperlinks URL is -1 instead of the actual moduleID.
What am I missing??


P.S.  Both files are in the same directory.

How about declaring a ModuleId property on the user control and passing the correct moduleid upon instantiating it?
Think of it: you're building a general user control that need a param to work ok, so I suppose the param can be passed uh?

- in your user control define a moduleid property
- then when you add it to a dnn module use this:
<Custom:ctrl id="cusctrl1" runat="server" ModuleId='<%=ModuleID%>'></Custom:ctrl>

I recommend not using the Late Binding syntax (i.e.. <%= ModuleId %>) as that can reck some havoc on the module caching and the skinning engine from DNN.

I would however recommend using either the Page_Load or Page_Init events to populate the usercontrol with cusctrl1.ModuleId = ModuleId. If you use the Page_Load event, make sure it's not inside a If IsPostBack = False Then line of code..

Actually, What you're missing is the ModuleConfiguration object, which seems to hold the ModuleId value.

So, on Page_Init you'll need to do something like this...

cusctrl1.ModuleConfiguration = Me.ModuleConfiguration

If that usercontrol already inherits from the PortalModuleBase, that property will already exist. If you're using the plain jane UserControl base class, you'll need to add the ModuleConfiguration property which is of type ModuleInfo.

I just looked at my modules which do this, and that's how I've gotten the ModuleId to be valid on sub-usercontrols.

uzi,  this sounds as though it will work.  I am using the PortalModuleBase so using this method I should be able to make it work.  I'll post back.

Setting the modulecontrol property for each sub-user control in the main page worked for me (problem here).

Yep worked for me too...

Yes, this is a great solution.

I would not recomend inherithing from PortalModuleBase for nested user controls. Convinience inheriting is a bad practice. What you need to do is expose a PortalModuleBase propoerty on a user control and then assign it in Page_Init. like this.

ctlSomeNestedUserControl.PortalModuleBase = Ctype(me,PortalModuleBase)

or if you do not need everything that is in portalmodulebase, you can expose on ModuleInfo property and do the same thing.