Hi Blair,
Thank you very much for this new insight.
The use of WixLib sounds good; the actual wxs files of product A are
already in a WixLib, so that they can be shared between the installer
and MSM. The only thing is that the repository of product B then has to
have access to the repository of
.
1) Run a couple of SQL queries against the MSM to remove them from the
two Module*Sequence tables. 2) Change from using MSMs and instead
generate/consume WixLibs instead.
If you do distribute MSMs publically then each idea I have has
limitations.
-Original Message-
From: Joost van Zoest
with blank or missing action names? Does your MSM pass
validation by itself?
Blair
-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Monday, January 30, 2012 12:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010
If you mean if I've used guids which are also used in the VC MSM, then
no. I've tested this by generating completely new guids for my merge
module, and still I got the warnings.
Thanks for the idea though, didn't think of this obvious error...
-Original Message-
From: Blair
On 27-Jan-12 17:28, Bob Arnson wrote:
I have made an installer in WIX which embeds 2 merge modules: the
Microsoft_VC100_CRT_x86.msm merge module, and my own module (let's
call this one MyMergeModule.msm for now). When I embed the VC merge
module before MyMergeModule, I get a lot of
I have made an installer in WIX which embeds 2 merge modules: the
Microsoft_VC100_CRT_x86.msm merge module, and my own module (let's call
this one MyMergeModule.msm for now). When I embed the VC merge module
before MyMergeModule, I get a lot of warnings that some actions can not
be merged from
6 matches
Mail list logo
