|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Versioning problem - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
rokka Member
|
Hi, we have got a problem with the version number of our application and the version number of the resource dlls. Everytime we raise the version number of our application the translation gets lost. This can only be solved when we run "Build all" in sizulizer. Is it possible the make the resource dlls version independed from the version of the application? Greets Andre
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, If you make a new build of your application (I think this is the reason for a new version number) you always should also update the localized resource dlls. You could use the SLMAKE tool of Sisulizer Enterprise in your build process to automate this task. This way you always have up-to-date resource files matching your application. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 05:26 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Versioning problem | |
Sisulizer software localization tool - Three simple steps to localize
