timmangan
Posts: 47
Joined: Fri Mar 30, 2018 1:17 pm

Per-build digital Signatures

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 the AppXManifest changes to match the cert.
While two builds may be defined, both the certificate, and subsequent change to the publisher field, are central currently. This means that you build one version, then swap out the cert and build again.
Catalin
Posts: 6732
Joined: Wed Jun 13, 2018 7:49 am

Re: Per-build digital Signatures

Hello Tim,

Thank you for your feedback!

I have added this on our TODO list of improvements and hopefully this will be added in a future version of Advanced Installer.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Catalin
Posts: 6732
Joined: Wed Jun 13, 2018 7:49 am

Re: Per-build digital Signatures

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
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Feature Requests”