Forum Discussion
How and why PublisherID, PackageFullName and CA's break the upgrade cycle
In the past I have complained about the method by which the subject field of the certificate (aka Publisher) is hashed and used in the Package Full Name as I suspected it would cause problems for Mic...
This issue seems to still occur as of today.
Dian Hartono Well I had intend to mean the Registry.dat as that's one of the places they are stored when a package is captured by the Microsoft MSIX packaging tool (see attached image). ANother copy is also stored in the User.dat file, so whichever source the installer uses I mean that one.
By the way, it would be nice to know if one of those is a mistake and need not be in the package. My tooling makes duplicate changes in both of those files when editing the package.
