0

Is there any way to view/migrate properties from an installation being removed to the new installation in a major upgrade workflow?

This shouldn't matter too much but here's my context. I'm using MigrateFeatureStates to prevent users from recreating the service during major upgrades. The problem I'm seeing is if a user specifies a custom folder location for the service feature the upgrade fails as the service still uses the custom path while the files are installed to the default location.

Service install/control

<ServiceInstall Id="MyServiceInstall" Name="MyService" DisplayName="MyService" Account="[user]" Password="[pass]" Type="ownProcess" Start="auto" ErrorControl="normal" />
<ServiceControl Id="MyServiceControl" Name="MyService" Wait="yes" Start="install" Stop="both" Remove="uninstall" />

Install sequence

<MigrateFeatureStates Sequence="1001" />
<RemoveExistingProducts Sequence="1020" />
<StopServices Sequence="1700" />
<DeleteServices Sequence="1750"><![CDATA[(NOT UPGRADINGPRODUCTCODE)]]></DeleteServices>
<InstallServices Sequence="5800"><![CDATA[NOT(MIGRATE)]]</InstallServices>
<StartServices Sequence="5900" />
Yan Sklyarenko
  • 31,557
  • 24
  • 104
  • 139
Jake
  • 733
  • 8
  • 23

1 Answers1

1

If you were starting from scratch you'd use the WiX remember property pattern, but if the first product has shipped it's too late.

If the install folder was saved in the registry you could recover it with a WiX registry search. Otherwise you could use a WiX component search. You'd use the component id of the service executable and the search will recover its path. You'd use that in a custom action to set the install folder to that location.

If you are using the WiX major upgrade element then it sets a property called WIX_UPGRADE_DETECTED if you're upgrading, so you could suppress the browse dialog if that property is set.

PhilDW
  • 20,260
  • 1
  • 18
  • 28
  • Thanks! I didn't know about the remember property pattern. I'll try use this going forward. The ComponentSearch would've worked too but our component Guids haven't been consistent.. – Jake Jun 24 '14 at 21:58
  • 1
    Personally I'd like to see a WiX RememberProperty extension. Basically abstract it so all you have to do is set a Persist attribute on the property element and that creates a PersistedProperties property similar to SecureCustomProperties. Then some custom actions could dynamically build out the registry table and store the data in a standardized location based on UpgradeCode. – Christopher Painter Jun 25 '14 at 13:24