On 29-05-2014 19:13, Phil Wilson wrote: > Yes, in this case scheduling RemoveExistingProducts before > CostInitialize should solve the problem if it's related to this: Yeah, that is what I figured. Unfortunately, that is not a legal scheduling. According to http://msdn.microsoft.com/en-us/library/aa371197%28v=vs.85%29.aspx, RemoveExistingProducts can be placed, at the earliest, after InstallValidate, which happens after CostInitialize. If I try to do it anyway, WiX gives me this error:
error LGHT0204: ICE27: 'RemoveExistingProducts' Action in InstallExecuteSequence table in wrong place. Current: Search, Correct: Execution So that doesn't seem like a viable solution, unfortunately. The earliest legal scheduling of RemoveExistingProducts is still too late. Any other ideas? > http://support.microsoft.com/kb/905238/en-us > > where MSI decides not to install the file but forgets that a major > upgrade is going to remove it. There was a thread on the subject > recently that a search for -RemoveExistingProducts - should find. > --------------- > Phil Wilson It looks like that's a slightly different problem, but the same root cause (MSI fails to take into account during the cost phase that the product is going to be removed) / Jesper ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
