Hello Liang,
As you already mentioned, this is indeed a bug of Microsoft. More details about this can be found in the following:
[BUG] Package cannot automatically update when the signing certificate has changed
The good news is that we might be able to work this around - until Microsoft fixes it.
To do so, we can proceed as it follows:
- in the newer version of your MSIX, we change the
"Package ID" slightly:
"Package Information" page -->
"Package" section -->
"ID" field.
- the above change will allow us to install the two version side by side
- now, in the second version, we will configure a PowerShell script to be executed when our application runs (at the first launch, for instance). This PowerShell script job is to basically remove the older version.
For more details about this, please have a look over the following:
1.
PSF: Trigger MSI installation from a MSIX package using PowerShell
where my colleague Dan explains how such script can be created.
2.
MSIX PowerShell cmdlets
where we can see what predefined cmdlets PowerShell offer us to work with MSIX packages.
Hope this helps!
Best regards,
Catalin