ROGG437063

I have been investigating a similar use-case and microsoft recommends to do strong naming with a self-signed key, so I don't see why that would also be used for authenticode...

I am also supporting this request, our developers need to migrate to trusted signing, but without support for clickonce in any of the other trusted signing tools, that is not...

This integration should probably use the SDK https://www.nuget.org/packages/Microsoft.Trusted.Signing.Client Do take care that the SDK linked in trusted signing docs is deprecated

@Jaxelr Sounds good, any estimate of when that will be merged? It would also still need integration with sign cli for vsto manifest signing, right?