admin管理员组

文章数量:1291026

I am trying to get a ClickOnce application signed properly, after publishing, including the application files (exe, dll, application file, manifest). Because I am using HSM (Specifically DigiCert One) I need to sign after running publish with msbuild. There is always some mismatch between the manifest and application files and the installation does not run

The signing is itself successful but when I try to install, I get the error

Application cannot be started. Contact the application vendor

Checking the log I see this:

Reference in the deployment does not match the identity defined in the application manifest.

The error is obvious, but I don't know what the correct action sequence is to get this working correctly.

After trying different thigs, what made most sense to me is:

  1. Removing the .deploy extension from the application files
  2. Signing exe and dll files
  3. Updating the manifest file
  4. Signing the manifest file
  5. Updating the .application file
  6. Signing the application file
  7. Restoring the .deploy extension

But it still resulted in the same error.

本文标签： ClickOnce Signing After PublishStack Overflow

版权声明：本文标题：ClickOnce Signing After Publish - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1741522238a2383256.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。