[wix-users] Previous package not found (and therefore not uninstalled) during major upgrade

[Steve Sanders]

I am positive because of the associated updater log, among other reasons,
which shows version 1.0.39-20180121191330+5e57981 (that's the semantic
version, the windows version being 1.0.39.39) applied 2018/01/23 11:57:11,
then the updater considers that version current when it checks for the next
update:
2018/02/16 19:30:03 INFO Checking for update, current version is
1.0.39-20180121191330+5e57981
(updater gets this version by running the installed program with the
"version" argument.)

Again, our custom actions are supposed to close our processes in the
upgrade case, but if upgrade case is not detected, they can't close the
processes.

I guess we could hack around this with some registry entries, but detecting
+ applying upgrades is one of the main reasons to use a tool like Wix I
thought. Again, this happens only intermittently, and didn't seem to happen
ever with Wix 3.9.

Thanks again, everyone, for taking a look.

On Tue, Feb 20, 2018 at 3:23 AM, Nir Bar via wix-users <
wix-users at lists.wixtoolset.org> wrote:

> The failing log says the the RESTART MANAGER is disabled so FilesInUse is
> used. FilesInUse can only detect applications with a window.
>
> However, this has nothing to do with upgrade detection. I've never
> encountered a false-false upgrade detection.
> Are you absolutely sure that another version is already installed?
>
>
>
> --
> Nir Bar, Independent WiX Expert. Creator of-
> JetBA: WiX WPF Bootstrapper User Interface Framework
>
> JetBA++: WiX Native Bootstrapper User Interface Framework
>
>
>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>