|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| combining assemblies - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
lachmayr Member
|
I'd like to see if I can have 2 sources and combine them into 1 satellite assembly. Is that possible?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, Sisulizer uses the input as a template for the output. It does not change the structure of logic of your source and binaries. Your idea would ask to change one of the main concepts of Sisulizer. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
lachmayr Member
|
Well, the reason I'd like to be able to do this is to build my \es-ES\App.resources.dll from my App.dll and \en-US\App.resources.dll for their Properties.Resources and XAML resources respectively. Not asking for any change in structure to existing binaries, just that final output file contains both XAML resources as well as the projects Resources. Doesn't Sisulizer already do something like this when using the App.csproj as the input? It builds one output file based on multiple input source code, right?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, If I get you right, then you ask to combine US and ES resources in one satellite assembly. To my knowledge does .NET not allow mutlilanguage resources. For standard resources this is possible and Sisulizer supports it there. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
lachmayr Member
|
Not exactly... For the default assembly (en-US), the Properties.Resources resources seem to stay in the main assembly (App.dll), while the XAML resources get put into the satellite assembly (\en-US\App.resources.dll), right? Now, Sisulizer can read the App.dll and output a \es-ES\App.resources.dll with all the Properties.Resources. And Sisulizer can also read the \en-US\App.resources.dll and output an \es-ES\App.resources.dll with all the XAML resources. But if I read in both the App.dll and \en-US\App.resources.dll, Sisulizer will output 2 separate instances of \es-ES\App.resources.dll. It would be useful to me to combine the 2 outputs into 1 file. -Stephen
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Stephen, The problem is that Sisulizer just creates the resources in the way .NET needs and expects them. If you try to leave the recommended path you have to change at least the logic in your application if not in the .NET framework. And that is exactly what Sisulizer does not do. E.g. some people asked if it would be possible to change the output path for the .NET assemblies. For Sisulizer that would be off course easy. But .NET would not find these files in other paths at runtime and so this freedom of choice is useless. So it is not Sisulizer limiting you but the platform. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 10:27 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > combining assemblies | |
Sisulizer software localization tool - Three simple steps to localize
