Bob Arnson wrote: It will update the shared component but it won't update the other product, so a repair operation can "undo" the patch. That's why merge modules are falling way out of favor...
Hello Bob, Thanks for your clarification. It seems I will have to adress all the products using the MSM with my patch. Fortunatelly this would be possible because all the products using my MSM are well-known to me (my MSM is not world-wide released - it is used only by my company's products). However, not all these products are using WIX so I do not have wixpdbs from their releases => I do not have wixmsts for all of them to send to pyro. However, all the product codes and any other potentially usefull informations are available to me. More, my product for which I have wixpdbs is localized (I have multiple MSIs), but the patches I shall deliver will not be localized, so I would like to build a patch using only one set of differences, no matter how many language-dependent versions I have. So far I don't know how to instruct pyro to address my patch to all MSIs unless I make differences for all of them and pass all these difference sets to pyro. Can you please advice me if it's possible to target multiple MSIs with only one set of differences and how ? Regards, Cristian ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
