Is there a way to maintain the same small Setup.exe and let is download the latest nupkg from the web instead?

[danielkornev]

Hi! I'm currently working on submitting my product to Microsoft Store, and found a few limitations:

1. Each new release has to be a separate package in the Microsoft Store metadata
2. In the future (starting with July 16, 2022) each release has to be code-signed
3. Yet many code-signing operations are provided on a limited basis (e.g. up 60 releases per year, see the image below from signpath.io)

With all that said, it would be much simpler if:

1. One could have a few major setup.exe files during the year
2. Smaller changes could be delivered by deltas

Is this possible to be done with Squirrel for Windows?

[anaisbetts]

This is not possible - your delta builds have to be code-signed (Squirrel.Windows doesn't care, but if you didn't sign them, your binaries would go from signed => unsigned, which would almost certainly trigger 3rd party AV).

I'm not sure that you can use this service pictured with Squirrel.Windows because Squirrel itself needs to control the signing process (you pass in certificate details into --releasify) - you need to just buy a real signing certificate. Here's a good list of places to get one: https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/code-signing-cert-manage