We've hit an interesting scenario in our work where we're not seeing one
of the MSM's getting applied in a re-install scenario.
We start off with some.msi that contains the following merge modules:
* a.msm
* b.msm
* c.msm
* d.msm
Some.msi now lays down all of the merge modules to disk as we would
expect them and everything is happy.
Now, we've updated some.msi (with the same ID and upgrade code), but
we've change out a couple of the merge modules, like so:
* a.msm
* b.msm
* d.msm
* e.msm
We have removed c.msm and added e.msm and execute it on the command line
like this:
msiexec /i some.msi /passive /l some.msi.log addlocal=all
reinstall=all reinstallmode=vamus
What we see is that c.msm is still on the disk (as it should be as other
packages are still referring to it), but e.msm has not been written out
to disk.
The question is this: How would we go about insuring that e.msm is
delivered like we think it should be.
Thanks!
Rory
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
