|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Error in BAML resource name when building with release configuration
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Error in BAML resource name when building with release configuration - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
ltagliaro Member
|
Hello, I noticed that BAML files are always created in obj/Debug folder, even when the configuration is set to Release. The final satellite assembly is correctly placed in bin/Release, but all the BAML binary resources inside it have a wrong name: they are called "..\debug\Window1" instead of "Window1" and so on. As a consequience, localized BAML resources are not loaded at runtime, and the user interface is displayed always in the default language. This problem only occurs when I am trying to build and deploy with the release configuration. If I use the Debug configuration, the problem does not occur. Thank you for your help Lorenzo
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
What version of Sisulizer you have (build number) Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
ltagliaro Member
|
Version 2010 Build 306 Lorenzo
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
ltagliaro wrote: Version 2010 Build 306 This bug has been fixed in build 307. Please update to 307. Jaakko
|
||||||||||||||||
| |||||||||||||||||
| Current time is 01:55 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Error in BAML resource name when building with release configuration | |
Sisulizer software localization tool - Three simple steps to localize