Hello,

I am trying now a few days to localize my DotNetNuke modules. I am really frustrated about the built in localization methods of DotNetNuke!!!

I created my Modules from several User Controls to create a modular system. So I was testing the user controls first without using DotNetNuke. Everything was working fine.

I was using standard Resource Files and added to all the labels, grids etc. meta:resourcekey="..." .

Everything was working outside of DotNetNuke!!!

Then I tried to integrate my user controls into my DotNetNuke Modules and my problems began!!!

I found out that DotNetNuke is using an alternative approach for localization, using the property resourcekey. But how can I localize for example a GridView Control??? I can't add the resourcekey property to a BoundField. I always get the error: The type
 BoundField has no public property called 'resourceKey'. I don't want to add some additional localization logic to my modules.

Why can't I just use standard ASP.NET localization with DotNetNuke!!!

I am absolutely despaired, because the localization is last part of my project and I've alrey exceeded the project budget.

So if anyone could help me, I will be very appreciate!!!

First of all, thanks for your quick response - Yes of course I did :-(.

In every post in this forum about questions regarding the localization, this answer comes as response :-( .

Did no one read the release date of this document - It's March 2006!!! It is not up to date - just like most of the remaining parts of the documentation...

I don't want to integrate another method call into my user controls just to translate a grid view as suggested at another post.

Again, I just want to use the very comfortable built in ASP.NET 2.0 localization using meta:resourcekey. I am wondering how DotNetNuke was switching the built in localization off!!!

If you are not familiar with the standard way:

you just have to add to your control you want to translate the property meta:resourcekey="lblTestLabel".

Now you have to add the key lblTestLabel to your Resource File, and you just have to add seperated by a dot the property you want to have translated e.g. lblTestLabel.Text to translate the text property....

Why can't I just do the same in DotNetNuke!?

DotNetNuke localization was introduced in DNN3 before ASP.Net 2.0 was released. It used to use the standard resource file format, but supports only text data with value attributes. Regarding the implementation, DotNetNuke localization has some analogies with ASP.Net 2.0 localization but is independent from it and has a different mechanism to retrieve languages and resource files to apply. If you want to implement enhancements, you are welcome to donate them to the core team.

As there have been minor changes to the localization system during the past 2 years, the localization guide is still up2date.