I'm assuming that you're installing the MSMs as files i.e. they're for your
end-users to use to build their own installers, therefore the fact that they
are MSMs is not relevant.

 

The component rules say you're not allowed to change the makeup of a
component. If all these MSMs are in one component you should break it into
multiple components, and change the product code to do a major upgrade. If
it is one component Windows Installer is likely detecting that the key file
has not changed and therefore it doesn't need to reinstall the component.

 

You can add components to new features for a minor upgrade, but I don't
think you're permitted to add components to an existing feature. In practice
this means you cannot remove c.msm even if it were a separate component. See
"Changing the Product Code" in the Platform SDK.

 

-- 

Mike Dimmick

 

  _____  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rory Clark
Sent: 16 May 2007 21:18
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Reinstalling with different MSM's...

 

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

Reply via email to