StrataFrame Forum

Getting localization error

http://forum.strataframe.net/Topic18581.aspx

By Jason Seidell - 8/19/2008

I have no clue why but one of my projects if I set to stop on all exceptions keeps stopping in the AppMain with the following exception. 

MicroFour.StrataFrame.UI.Localization.MessageLocaleID = MicroFour.StrataFrame.UI.Localization.GetActiveLanguage("ReportsSplitAuto")

The file [Message_Languages.xml] could not be found.  The localization languages table could not be loaded.

I don't have anything special setup for localization or messaging so I just commented out the line, but any ideas of what's missing???

Jason

By Dustin Taylor - 8/20/2008

If you are setting that local ID and are using any messages at all, you'll need to configure your message store. We recommend using embedded xml files, but you can also store them externaly or in SQL.

In the StrataFrame help there are step-by-steps for configuring all three under Application Framework->Localization & Messaging->Messagign->Configuring the Message Store. Here is the short of configuring embedded xml files.

  1. Create a messaging project within the Localization and Messaging Editor and populate it with the initial message objects.
  2. Select the Generate XML button on the Localization and Messaging Editor command bar to export the messaging project into a series of XML files.
  3. Add a Localization Files folder to your Visual Studio project.

    Note: While it is recommended to create a separate folder in which to house the messaging XML files, this is not a strict requirement.

  4. Add the localization XML files to the Visual Studio project folder.

    Note: If the Locale ID will be manually assigned and the Localization.ShowAvailableLanguages() or Localization.GetActiveLanguage() methods will not be called, the Message_Languages.xml does not have to be included. However, if the application will allow the end-user to choose their language using the ShowAvailableLangauges() method, the message_Langauges.xml file must be included.
  5. Now that the messaging files have been added, they need to be specified as an embedded resource. To embed each of the messaging files as a resource, simply select the file, go to the property sheet, and change the Build Action to Embedded Resource.
  6. When using Embedded XML files, neither the MessageKeyType nor the MessageXmlPath is required within the AppMain.vb or the program.cs files.  As such, these lines can be removed. 
    Localization.MessageKeyType = MessageKeyDataType.XMLLocalization.MessageXmlPath = ""
  7. The final step in configuring the message store is to set the Locale Id to the match the desired language.  This can be hard coded, or can be based off of the LCID of the CurrentCulture.