i've added another check in Create-Win32App.ps1 which extracts the GUID in app.json:
"UninstallCommand": "MsiExec.exe /X \"{5140803c-3de4-49a7-9565-78be00a11a16}\" /quiet",
and tries to find the real GUID from the .msi package itself with
$msiID = Get-MsiProductCode(Join-Path -Path $SourceFolder -ChildPath $($appdata.PackageInformation.SetupFile))
so when evergreen updates an msi package and the publisher has changed the GUID, we can go for sure that we have a correct uninstall script.
Hi Aaron,
i've added another check in Create-Win32App.ps1 which extracts the GUID in app.json: "UninstallCommand": "MsiExec.exe /X \"{5140803c-3de4-49a7-9565-78be00a11a16}\" /quiet", and tries to find the real GUID from the .msi package itself with $msiID = Get-MsiProductCode(Join-Path -Path $SourceFolder -ChildPath $($appdata.PackageInformation.SetupFile))
so when evergreen updates an msi package and the publisher has changed the GUID, we can go for sure that we have a correct uninstall script.
Kind regards, Constantin