FYI Upon upgrading to 21.2.1 my MSIX package builds started failing during the signing process with an error indicating "No siguature was present in the subject". I am using a custom signing with a Digicert Keylocker based key. The failure also existed previously, however the messaging was quite dif...
In version 21.1 I have noticed the following behavior. If I update my Visual Studio traditional app using a new version, and then open the existing AIP file (it will detect the new version and notify me of that), and then immediately ask to build the MSIX package, it will now fail claiming an issue ...
Referring to this article: https://www.advancedinstaller.com/user-guide/qa-trial-using.html The customer would like to register the application by using a command line argument with the registry key, rather than the dialog GUI. The reason for this is that the application will be used in a non-persis...
ISSUE: To sign MSIX files AI must extract and add the correct publisher string into the AppXManifest. I am still struggling with that, and the wrong publisher ID is now being used, but signing of other types of files seems fine.
I just upgraded from 19.5 to 19.7. I noticed that when I build, the display of the lower window no longer automatically jumps from Notifications to Output. When starting the build I liked seeing the output tab.
Microsoft has identified a process that will allow a MSIX package to be upgraded when the new version of the package is signed with a different code signing certificate. The steps are outlined https://docs.microsoft.com/en-us/windows/msix/package/persistent-identity . Why is this necessary? Because ...
Once again, an upgrade to AdvancedInstaller version broke an existing build. This time I upgraded from 19.1 to 19.3, but the last few times I upgraded the package has been broken. In this case, the creation of the MSIX file succeeded, however signtool failed with an indication of a bad package. Inve...
If you have a project that you want to deliver using MSIX from the Microsoft Store and from your own website, you currently must make two AIP projects. The Microsoft Store version of the package must use a Microsoft supplied (ugly) Publisher field and a temporary cert provided by them to match. The ...
Using AI 18.9.1 and updating a package. The UI detects the new version from the primary app, but the internal AppXManifest file did not get the updated version. In this case, only the 4th field of the version had changed in the app (causing an unnecessary popup in the detection logic that is only re...
After upgrading both VS and AI, the aip project refuses to load in visual studio. I removed and re-installed the plugin (which is still 18.9 in the marketplace) and this not help. The project does open and build correctly when launching AI against the api file manually outside of Visual Studio. C:\S...
This is a feature request. It looks for support for a scenario where a developer has an application that is distributed as MSIX both through the Microsoft Store and via private site, requiring two slightly different builds from the same AIP: A different certificate is used. The publisher field in th...
