0

If multiple versions of the same product are installed, can a property be used to check for the a newer version and add a condition message and prevent an uninstall?

  • WebSite 1.0.0 - Base Files (MajorUpgrade)
  • WebSite 1.0.1 - Minor updates to files
  • WebSite 1.1.0 - Base Files (MajorUpgrade)

Use case: Both WebSite 1.0.0 and WebSite 1.0.1 are installed on the webserver using the MSI package. When WebSite 1.0.0 is being uninstalled, I need to be able to prevent this if a newer version exists.

I considered using conditions but not sure if this is the best way to go. 

<Condition Message="Newer version of the product must be removed">
    Installed OR PRODUCTVERSION > 1.0.0
</Condition>

When WebSite 1.1.0 is installed it will remove the previous version because it has the base set of files needed.

Jerode
  • 490
  • 4
  • 15
  • If you need to prevent the manual uninstall of 1.0.0 then you need a search for (say) component Ids that exist in the later versions. Or you need the later versions to create registry entries that 1.0.0 can know in advance and search for during uninstall. The major upgrade search won't find anything because it doesn't run during uninstall. You need a search, component, registry or something that 1.0.0 knows will be in a later version. Then use that property in a launch condition to prevent uninstall. I'm assuming that you literally mean "prevent uninstall" of 1.0.0 and it's no typo. – PhilDW Apr 03 '15 at 18:23
  • Okay, this is a good proposal. And yes, I do mean to prevent an uninstall. Could you write up an answer for this with the registry example so I can mark appropriately? – Jerode Apr 06 '15 at 13:55

2 Answers2

2

The MajorUpgrade element handles all of this with 1 attribute.

<MajorUpgrade DowngradeErrorMessage="A newer version of [ProductName] is already installed." />

If you are using IsWiX (CodePlex) project templates this is authored by default out of the box. The idea is to cover the most common requirements and use cases so you don't even know you have a problem in the first place.

Christopher Painter
  • 54,556
  • 6
  • 63
  • 100
  • Okay, I will give it another shot. I tried this use case and I could remove the WebSite 1.0.0 and WebSite 1.0.1 still remained installed. I touch base shortly. – Jerode Apr 02 '15 at 20:15
  • I did run through using the MajorUpgrade tag and did not get the expected result. MajorUpgrade will remove the previously installed product on install and this is not the result I need. For file updates I need the original files to remain. – Jerode Apr 02 '15 at 23:29
  • MajorUpgrade can also detect products using the DetectOnly attribute. That's what DowngradeErrorMessage authors. – Christopher Painter Apr 02 '15 at 23:33
  • So should I not be using the MajorUpgrade on the 1.0.1 version of the installer? My apologies for not completely understanding. When doing the 1.0.1 version I fully expect both products to remain installed until the next major upgrade. The reason is that when removing the previous version the site will be down while the entire file structure is rebuilt. – Jerode Apr 02 '15 at 23:45
1

If you need to prevent the manual uninstall of 1.0.0 then you need a search for (say) a component Id that exists only in the later versions, and you'd need to know what they are in the older versions so that the older versions can predict the future. Or you need the later versions to create registry entries that 1.0.0 can know in advance and search for during uninstall. The major upgrade search won't find anything because a major upgrade FindrelatedProducts search doesn't run during uninstall. You need a search, component, registry or something that 1.0.0 knows will be in a later version. Then use that property in a launch condition to prevent uninstall.

Another possibility would be a custom action that calls MsiEnumrelatedProducts() or equivalent on the upgrade code. This will return a series of ProductCodes for which you can call MsiGetProductInfo() to get the product version, and then check for whatever values are relevant. This has the advantage that the older product doesn't need to know in advance registry entries or component Ids because upgrade codes are more predictable and they are more unlikely to change in a series of products.

PhilDW
  • 20,260
  • 1
  • 18
  • 28