Context: We are multiple developers that are working on a single Office addin. Our continuous integration (CI) server creates deployable artifacts.
However, Visual Studio enforces every developer to sign the ClickOnce manifest (disabling the checkbox "Sign the ClickOnce manifests" in the project properties will re-check it on the next build). Thus every developer needs to be in possession of the signing certificate.
Is there a way to disable signing the manifest for the developers?
Note: We do not want to eventually deploy without a signed manifest, but we want to keep the signing certificate on a single machine.
We now solved this for us as follows:
While this does not disable signing on the development machines, it avoids the problems associated with sharing the trusted certificate on all development machines.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With