签署 ClickOnce 清单复选框在发布时保持默认选中状态
我正在尝试使用 ClickOnce 获取 .NET 解决方案进行发布，而无需在 Visual Studio 2008 SP1，但我没有任何乐趣。具体来说，每次我发布时，都会重新选中名为“签署 ClickOnce 清单”的复选框。奇怪的是，另一位开发人员说他可以在同一解决方案上发布并且不进行检查。
我看到了另一个 Stack Overflow 问题，如何不签署 ClickOnce 清单。但我认为根据 Microsoft 的帖子，您应该能够使用 ClickOnce 进行发布，而无需登录 Visual Studio 2008 SP1，如何：签署应用程序和部署清单。
但是，无论进行多少次重新发布和取消检查，我都无法在不生成某种证书的情况下继续。
I am trying to get a .NET solution to publish using ClickOnce without signing the manifests in Visual Studio 2008 SP1, but I am having no joy. Specifically the check box called "Sign the ClickOnce manifests" keeps getting re-checked every time I publish. Strangely, another developer says he can publish on the same solution and leave this unchecked.
I saw the other Stack Overflow question, How to not sign a ClickOnce manifest. But I thought you are supposed to be able to publish using ClickOnce without signing in Visual Studio 2008 SP1 per Microsoft's post, How to: Sign Application and Deployment Manifests.
But no amount of re-publishing and un-checking allows me to continue without generating some sort of certificate.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我遇到了同样的问题，但我从未弄清楚如何“解决”这个问题。我的解决方案是签署每个发布。但是，与应用程序关联的证书是一个“虚拟”证书，我允许 Visual Studio 生成该证书，并将到期日期设置为最大可用日期。
您的应用程序仍将被签名，但您应该担心您的用户必须卸载并删除它。证书过期后重新安装您的应用程序。
I had the same problem, and I never figured out how to "fix" this problem. My solution has been to sign every publish. However, the certificate that I associate with the application is a "dummy" one that I allow Visual Studio to generate, with the expiration date set to the maximum available date.
Your application will still be signed, but you should have to worry about your user's having to uninstall & re-install your application when the certificate expires.
我最终找到了一个修复程序。通过右键单击原始发布计算机上的证书文件并安装它。我不知道为什么需要这样做。也许第一次用于发布的证书（由不同的开发人员）不匹配，而我的 VS 正在生成另一个证书。
I eventually found a fix.. By right clicking the certificate file from the original publish machine and installing it. I don't know why this was required. Maybe there was a mismatch in the certificate first used to publish (by a different developer) and my VS was generating another.
我也有同样的问题。事实证明我的证书已过期，我可以通过 使用 MMC 中的“证书”管理单元。我又创建了一个新的测试证书并使用了它，现在一切都很好。
I had the same problem. It turns out my certificate had expired, which I could verify by using the "Certificates" snap-in in MMC. I created a new test certificate for another year and used that, and it's all good now.