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 version for your own website will want to use a Cert from a Public CA and will have a different Subject/Publisher.

It would be ideal if this could be accomplished with a single AIP project with two builds. This would require the ability to define per-build certificates, and either per-build Publisher fields or just pull from the cert each time.

Hello Tim,

Thank you for your suggestion.

I believe we already have this on our TODO list of improvements as you requested this quite some time ago in this thread:

Per-build digital Signatures

I will increase the priority for this ticket and hopefully this improvement will be added in a future version of Advanced Installer.

Unfortuantely, this had quite a low priority because no other users have requested this feature.

Best regards,
Catalin

Hello Tim,

This improvement has been added in version 19.7 of Advanced Installer, released on July 18th, 2022.

However, this is not quite the "per-build" digital signing you have asked for.

The improvement our dev team added is as it follows:

- it allows you to build 2 MSIX packages from the same AIP file (one for Sideloading and one for the Microsoft Store)

- after the build, the PublisherID will be different

Best regards,
Catalin