Hi All,

Trying here to get localization (via resource files) working for custom module view control used with ASP.NET MultiView control. No luck. :(

Is it supposed to work? Am I doing something wrong failing to get it working? (I have checked - when DNN Label control is used outside of ASP.NET MultiView control within the same "host" view control  then localization works OK. So there is a chance I mistyped the filename of the hosted in ASP.NET MultiView control while creating resource file for it. But I have checked it and it seems to be correct...

Is ASP.NET "guilty" in my case mangling control names, and then DNN core can't find proper item from resource file?

In general:

- Is localization supposed to work OK for controls hosted on ASP.NET MultiView or Wizard controls? (Expected answer is "YES" because as Sebastian noted in one the threads here DNN Installation is implemented using ASP.NET Wizard control.) If localization doesn't work by default in this case then I should manually implement for custom controls hosted on Multi-View or Wizard controls?

- Is localization supposed to work OK (by default with proper resource files) for formview, detailview and gridview ASP.NET controls when they used with templates and that latter templates do use DNN label and command button controls etc.?

- Will localization work OK if I will use LiveTabs module? (
http://www.snowcovered.com/Snowcovered2/Default.aspx?tabid=242&PackageID=15552)

Please point on DNN modules where wizard, multiview, formview, detailview and gridview ASP.NET controls are used for me to check how they are organized.

Thank you.

--Shamil

Thank you, Sebastian,

That helped but there are some issues still:

Stacked view controls located on ASP.NET MultiView control do not get localized properly even when ResourceKey ="{{ResourceKeyCode}}" is used (the same View control displayed independently on a page within a module does have localization working properly). When I have used ResourceKey for one of the SharedResource entries it did worked well for stacked view control. So as far as far I see standard localization doesn't seems to work for stacked view controls (bug/feature).

What could be a workaround solution? I suppoose that could be a direct DNN API call Localization.GetString(...) for Text property?

Text='<%# Localization.GetString("MyControlKey",LocalResourceFile) %>'

Not sure if that will work but if it will then similar approach could help to localize HelpText...

And I can also make custom shared resource files, put them under \AppGlobalResources and use custom wrapper method(s) around Localization.GetString(...) to use that shared resources for localization..

That should work well, I suppose.

Thank you.

--Shamil