I am trying to integrate DevExpress controls into my Modules. Under normal use in an aspx page in a normal web site they work fine. But when put into a module in DNN the localization fails.

For example they support localization as such:

<dxe:ASPxButton ID="ASPxButton1" runat="server" Text="ASPxButton" meta:resourcekey="btnReturnRS"> </dxe:ASPxButton>

The entry in the resource file is btnReturnRS.Text with the Value Return

For some reasom under DNN the resource cannot be found and is not updated like it does under a normal aspx page. Is this a bug or does the core need to be changed to recognize these 3rd party tags? If it does is there some where I could start?

Walt

this should work: (assuming your modulecontrol's filename is moduleview.ascx)

• put the control in your ascx file like this (leave out "meta:">: <dxe:ASPxButton ID="ASPxButton1" runat="server" Text="ASPxButton" resourcekey="btnReturnRS"> </dxe:ASPxButton>
• make sure you created a resx file with the name moduleview.ascx.resx in a folder app_localresourcefiles. This folder should be at the same level as your modulecontrol
• make sure you've created a key with this name: btnReturnRS.Text
• view the module in dnn, dnn should localize the text property of the control

if this is not working, the workaround is doing this in code behind:

ASPxButton1.Text = Localization.GetString("btnReturnRS",LocalResourceFile)

DNN Blog | Twitter: @erikvb | LinkedIn:

For those that care I have found where the problem lies but not how to fix it. IT appears that devExpress uses the microsoft best practice of using meta:resourcekey= when the resourcekey is not a property of the control as is the case of devExpress controls. This causes dnn to fail when loading the user control (must not understand the meta:). When used outside the DNN enviornment it works fine as a user control and I can provide an example project if anyone is interested. Can this be reported as bug or must it be requested as suggestion for further enhancement?