Describe the bug
I've been testing packaging a VB6 app (yeah, I know) with MSIX, to simplify deployment and upgrades internally (this is not published to a Store, only used internally at the company premises). Installations work fine, and the application works as expected. However, if I upgrade to a newer version, the included .ocx components show up as "not registered" and the application stops working.
If I uninstall the application completely, and just install the latest version instead, it work as it should once more. Something is causing this on upgrades only - even minimal ones (just changing the version number in the Appxmanifest.xml is enough to trigger this).
To Reproduce
Package an application which includes registering .ocx components with either the MSIX packaging tool or the command line.
Sign the application with a valid certificate.
Install the application - the application works as expected, no errors reported.
Package an updated version, without any real changes (e.g. just bump the version in the manifest)
Upgrade to that version
The application now reports that the related .ocx files are not registered and fails to work.
Uninstall the application.
Install the latest version directly - the application works as expected (no errors).
Expected behavior
An upgrade of the packaged application should not trigger components to show as not registered.
Screenshots
Not sure it's applicable, but I can provide more info if needed. ;)
Project MSIX SDK
Describe the bug I've been testing packaging a VB6 app (yeah, I know) with MSIX, to simplify deployment and upgrades internally (this is not published to a Store, only used internally at the company premises). Installations work fine, and the application works as expected. However, if I upgrade to a newer version, the included
.ocxcomponents show up as "not registered" and the application stops working. If I uninstall the application completely, and just install the latest version instead, it work as it should once more. Something is causing this on upgrades only - even minimal ones (just changing the version number in the Appxmanifest.xml is enough to trigger this).To Reproduce
.ocxcomponents with either the MSIX packaging tool or the command line..ocxfiles are not registered and fails to work.Expected behavior An upgrade of the packaged application should not trigger components to show as not registered.
Screenshots Not sure it's applicable, but I can provide more info if needed. ;)
Platform Windows 10, Windows 11