MonoX can be fully localized using two different approaches. First one is standard: it involves translating MonoX resource (.resx) files (available from our support team on request) and sending it back to us for recompilation and inclusion to the installation package. This approach is quick and simple, and is more suited if you plan to develop multiple projects on top of MonoX - once you got a localized version, it is easy to open as many sites as you want with that particular language.

Additionally, MonoX includes support for completely interactive localization that does not require recompilation of the project, as all resources are stored in the database. This gives users more power and flexibility, since it would be impossible to localize all resources at run time (both built-in and custom ones) using only a "resx approach". It is possible to export values from database to resx files and vice versa, both for a single page/control or for a whole portal at once. To start using this approach you will have to change the default ResourceProviderModel in the web.config file and set it to DBResourceManager. This will enable the Portal localization management utility (found under "Other tasks" on the main administrative screen), that does the real job for all portal pages and controls.

This pane allows administrators to localize each and every localizable resource in the portal. Note that MonoX uses translation engines to suggest a correct translation for each text.

Regardless of the active resource provider model, administrators can dynamically add or remove languages from a list of supported portal languages in the Language manager administration section.

Note that everything I said above applies to the localization of the base MonoX package. You can choose additional custom scenarios for your projects built on top of MonoX, it will not interfere with any other technique.

I am trying to convert MonoX 4.5 version to DB based localization.

I changed the defaultProvider to DBResourceManager after generating the source and string for Chinese language.

when I am running the project it is giving me following error:

Line 462:        public static string AdminHeader_imgLogo_AlternateText {
Line 463:            get {
Line 464:                return ResourceManager.GetString("AdminHeader_imgLogo_AlternateText", _resourceCulture);
Line 465:            }
Line 466:        }

Hi abhi00729, 
have you done a recent MonoX upgrade? If yes, have you followed the MonoX upgrade instructions ?

At first look, this looks like an issue caused by an older version of LLBLGen dlls, please first check that you've upgraded those.

Let me know if this helps.

Regards,
Vedran

Hi vzakanj,

When I debug the issue I found it is coming from LLBLGen Dlls only.

Currently we are using version 4.5.3017.

I tried upgrading the LLBLGen dlls from version 4.5.3103 downloaded from MonoX site.

Upgrading LLBGen Dlls didn't worked, and we can not upgrade complete site as lots of changes has been done in the application related to our business.

I found source of the error is from dll : SD.LLBLGen.Pro.ORMSupportClasses.NET20

Please suggest if there is any other way to identify or rectify the issue.

Hello,

These types of errors occur if LLBLGen 'ConstantsEnums.cs' is not re-generated properly. However, this does seem to be coming from MonoX's DAL. Did you make any changes to the MonoX source code?

Regards

Hi Mzilic,

We did made some changes in the MonoX source code to make it work with our application, however we have not made any change in the source code of MonoX's DAL project.

Hi mzilic,

Also if you can explain how to regenerate 'ConstantsEnums.cs', I can try that, it might help.

Hello,

You need to run the LLBLGen utility to regenerate the DAL.

Regards

Please tell me where I can find the LLBLGen utility.

Regards