签署引用的程序集后生成错误 [英] Build error after signing referenced assemblies

查看:196
本文介绍了签署引用的程序集后生成错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我遇到一些签约的组件就已经高兴地建立与pre-签约后,建立在我的项目的错误。在错误列表中,我看到了这样的错误:

I'm encountering build errors in my project after signing some of the assemblies it has been happy to build with pre-signing. In the error list I'm seeing the errors like:

类型'XXX'在未引用的程序集的定义。您必须添加一个引用程序集XXX,版本= [正确的版本],文化= [正确的文化],公钥=空[不正确公钥标记]

The type 'XXX' is defined in an assembly that is not referenced. You must add a reference to assembly 'XXX, Version=[correct version], Culture=[correct culture], PublicKeyToken=null [incorrect public key token]'

在回复到未签名的程序集(仅code不同的是在引用的程序集存储在共享密钥的签约信息和他们的解决方案),一切又构建。

When reverting back to the non-signed assemblies (only code difference is the signing information in the referenced assemblies and their solution which stores the shared key), everything builds again.

不幸的是,这些文件需要签名,所以我想知道是否有人遇到过这个问题?

Unfortunately, these files need to be signed, so I'm wondering if anyone has encountered this issue before?

谢谢, 罗布

推荐答案

感谢大家对他们的答案。

Thanks to everyone for their answers.

事实证明,这是没有任何关系的事实,大会已经成为签署。有简单的其他程序集仍在引用,我还没有发现旧签名的版本。

As it turns out, it was nothing to do with the fact that the assemblies had become signed. There were simply other assemblies that were still referencing the old signed versions that I hadn't spotted.

...因为通常情况下,错误是椅子和键盘之间。

...as is usually the case, the error was between the chair and the keyboard.

这篇关于签署引用的程序集后生成错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆