Thanks for the reply (Schedule major upgrade late and ensure Component Rules
are followed. ) Rob.

I'm not sure I follow.

Hopefully I'm following the component rules as all resources used more than
once are only installed via one MSI in the GAC - lets call it
SharedComponents.msi.

In my (simplified) chain, I have
-ProductA.msi
-ProductB.msi
-ProductC.msi
-SharedComponents.msi.

SharedComponents.msi gets installed when either product A,B or C are
installed. 

If I schedule a major upgrade late (schedule RemoveExistingProducts after
InstallFinalize) and define the MsiPackage in the chain with a DownloadURL,
will this effectively
a) Skip downloading the SharedComponents.msi as it will already be in the
cache
b) run but ultimately leave the resources untouched  as it would (usually)
have no updates and no removals due to being the same MSI ?

Thanks again.

Sorry if this is a silly Q - the problem I have is that we generally only
have to update our installers every 6-8 months, by which time I've forgotten
everything <sheepish grin>.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Leave-components-installed-between-upgrades-but-not-permanent-tp7596436p7596468.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to