Hi! I have read following topic: Minor upgrade issue revisited <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Minor-upgrade-issue-revisited-td707681.html> New file not installed <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/New-file-not-installed-td6696061.html#a6700099> How Update / Upgrade strategy (small, minor, major) affect file overriding? <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-Update-Upgrade-strategy-small-minor-major-affect-file-overriding-td1304357.html>
I`m trying to make my product minor update(equal ProductCode, new product version is higher): installing the assembly components with the same component GUID and same assembly version(but new assemblies are recompiled), install scope - per-machine. After the update obsolete msi was not removed. In the Package Cache folder i get: Obsolete msi, /Will not uninstall package: MyProduct, found dependents: 1/ New bundle, New msi. After removal new bundle, some files are still existing. And old version of the product was not removed. What can I do? - always change my assembly component GUID. Do I have to change component GUID every time, if assembly was changed? - use major upgrade only. or something else? Alexey. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Obsoleted-msi-exists-after-minor-update-tp7583777.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
