ClickOnce signing via Azure Key Vault


I have a server with Jenkins on it, which handles building a WPF application with ClickOnce as a deployment option. I have used a set of commands for MSBuild and mage.exe to produce an application file with deployment and application manifests signed by a provided *.pfx file.

Now the decision was made that the pfx file will not be provided. Instead, all keys were moved to the Azure Key Vault.

My question is - what will be a correct flow to make manifest signing for the ClickOnce application work with Azure Key Vault? I just don't understand how to execute the mage -update correctly with no path to provide as -certfile argument.

1 comment
Comment actions Permalink

The post seems to be a copy of and has nothing to do with CLion.


Please sign in to leave a comment.