[wix-users] Caching of ExePackage breaks on Upgrade
AFMG Anton Herzog
anton.herzog at afmg.eu
Mon Jul 20 01:03:49 PDT 2020
My installer includes an ExePackage. It didn't change its version yet, so upgrading does not install the package again. I use "DetectCondition" for that.
<ExePackage Id="Package"
DetectCondition="Package_Version <= Package_InstalledVersion"
SourceFile="..\path\to\package\setup.exe"
UninstallCommand="WorkingUninstallCommand"
InstallCommand="WorkingInstallCommand"
Cache="always">
<Payload SourceFile="..\path\to\payload" />
...
</ExePackage>
When installing and uninstalling a version, everything works as expected. Now I upgrade the Bundle without including a newer version of the ExePackage.
* Describe the behavior you expected and how it differed from the actual behavior.
I expect to be able to uninstall the upgraded bundle, even when the original installer was moved. What happens is that it prompts me for the source as soon as the installer is not at the same place anymore.
This behaviour seems wrong to me. Shouldn’t the cache of an ExePackage stay intact or get cached again when updading the whole bundle without touching the ExePackage itself?
More information about the wix-users
mailing list