Clickonce is still used by many applications in the .Net environment. It is now a requisite for code signing to have far more stringent keys. A common solution is HSM backed in the Azure Keyvault.
It is not currently possible to sign the manifests using a key stored in an azure keyvault. There is an external tool that does a reasonable job, but has to rely on .Net framework.
Can you please provide a method to either utilize an HSM key, or at least provide interface points where we can intercept and validate a digest so we can extend and do it ourselves. It is currently a nightmare to deploy any .NET app through clickonce with a properly secured key
Clickonce is still used by many applications in the .Net environment. It is now a requisite for code signing to have far more stringent keys. A common solution is HSM backed in the Azure Keyvault.
It is not currently possible to sign the manifests using a key stored in an azure keyvault. There is an external tool that does a reasonable job, but has to rely on .Net framework.
Can you please provide a method to either utilize an HSM key, or at least provide interface points where we can intercept and validate a digest so we can extend and do it ourselves. It is currently a nightmare to deploy any .NET app through clickonce with a properly secured key