On 05-Aug-14 04:36, Tobias S wrote:
Here working with Satelite MSIs or duplicating the installer logic across
several MSIs or transforming an MSI seems not the first choice...
It depends. You can still have a single source. Seems preferable to me
than transforms.
--
sig://boB
Ok I see. For e.g. satellite assemblies ok.
But I think at the localized strings e.g. for the main exe related to
a) File Extension Registration
b) Ugly but sometimes used: CustomAction strings which need localization
Here working with Satelite MSIs or duplicating the installer logic across
Hi all,
Previously I thought Bundles can be designed by creating a multilingual BAL
and bundle that with (a) monolingual english MSI(s). But now I mention
small things that make it inevitable to have MSIs with transforms e.g. for
things like Description + Command localization for File Extension
On 04-Aug-14 10:43, Tobias S wrote:
What are the best approaches for MSIs within multilingual bundles?
Keep neutral resources in one package, localized resources in another
package, one per language (i.e., lang pack).
--
sig://boB
http://joyofsetup.com/
4 matches
Mail list logo