问题描述
我最近购买向GlobalSign的Authenticode证书和我有我的签名文件进行部署问题。有一对夫妇的由项目产生的，然后放入的.msi .exe文件。当我与signtool签署.exe文件的证书是有效的，它们运行良好。问题是，当我建立的.msi（使用Visual Studio安装项目）中的.exe文件失去其签名。因此，我可以签的.msi它建成后，但已安装的.exe文件继续整个未知发布者的企业。 ？我怎样才能保留这些文件上的签名要安装的客户端机器上
I recently purchased an authenticode certificate from globalsign and am having problems signing my files for deployment. There are a couple of .exe files that are generated by a project and then put into a .msi. When I sign the .exe files with the signtool the certificate is valid and they run fine. The problem is that when I build the .msi (using the visual studio setup project) the .exe files lose their signatures. So I can sign the .msi after it is built, but the installed .exe files continue the whole "unknown publisher" business. How can I retain the signature on these files for installation on the client machine?
推荐答案
Visual Studio创建在编译的时候两个文件夹： OBJ和bin。事实证明，至少在我的情况下，输出将始终从OBJ文件夹到bin文件夹复制。我登录的bin文件夹中的可执行文件只把他们覆盖，然后打包成MSI。签署可执行文件的文件夹中的obj解决了这个问题。
Visual Studio creates two folders at compile time: obj and bin. Turns out, at least in my case, the output will always be copied from the obj folder into the bin folder. I was signing the executables in the bin folder only to have them overwritten and then packaged into the msi. Signing the executables in the obj folder solved the problem.
这篇关于如何签订的Visual Studio安装文件的.msi的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！