View previous topic :: View next topic |
Author |
Message |
sdcronshaw
Joined: 08 Oct 2008 Posts: 2
|
Posted: Wed Oct 08, 2008 3:30 pm Post subject: Problem building Deployed (Binary) Localization assemblies |
|
|
Hi -
We are currently experiencing issues when building Binary localizations thru Globalizer; the generated content is different (i.e. missing translations) than when we generate localized RESX files thru Globalizer and build said RESX files in MS Visual Studio.
The generated DLLs are not of the same size and when we attempt to open one of the Globalizer-created DLLs in MS VS, we get an error "Cannot enumerate resources in the executable". Although the Globalizer-generated Binaries are missing translations that are contained in the VS-built binaries, the Globalizer binaries are sometimes larger than their VS counterpart.
We are experiencing this same "missing content" problem when generating Binaries from either the Translator edition or the Programmer edition of Globalizer.
Any assistance would be greatly appreciated.
Regards,
Scott |
|
Back to top |
|
|
sdcronshaw
Joined: 08 Oct 2008 Posts: 2
|
Posted: Wed Oct 08, 2008 5:59 pm Post subject: Additional information |
|
|
Upon further analysis, it appears that the internal resource namespaces within the Globalizer-generated binaries differs from the namespaces in the VS-compiled versions.
As an example, the resources associated with "MyCalendarView" form:
VS Compiled: ABC.Application.UserInterface.Windows.HomeModule.Calendar.MyCalendarView.de.resources
Globalizer generated: ABC.Application.UserInterface.Windows.HomeModule.Calendar.MyCalendarView.MyCalendarView.de.resources
Note the additional "MyCalendarView" in the generated binary's resource name.
Please advise.
Regards,
Scott |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Wed Oct 08, 2008 9:20 pm Post subject: |
|
|
Globalizer.NET deduces the required compiled resource names based on the default namespace for the project. If you don't define controls/forms in the default project namespace then you may need to change the ResourceName in Globalizer.NET (in the Control/Form properties tab) to match the fully qualified typename of the control/form.
As you may have discovered .NET Reflector is a good tool for analysing these sort of issues. You can load the satellite and main assemblies into Reflector to determine why resources may not be loading. _________________ Infralution Support |
|
Back to top |
|
|
|