如何更新 ASP.NET 网站中的强命名 DLL 以使用较新版本的延迟签名 DLL?
在调试 LinkedInToolkit 时,我下载了 来自 git 的 DotNetOpenAuth 源。现在我已经添加了参考,在编译来自 LinkedInToolkit 的预构建网站时出现以下错误
无法加载文件或程序集 DotNetOpenAuth 版本 3.4.7.11039。 强名称签名不能 已修改....
考虑到DotNetOpenAuth DLL是延迟签名的,如何让我的网站编译并运行?
我搜索了 web.config 和参考文献,以查找任何提及强命名 DLL 的内容。还有哪里可以进行强名称检查?
In debugging the LinkedInToolkit, I downloaded the DotNetOpenAuth source from git. Now that I've added the reference I'm getting the following error when compiling the prebuilt websites the come from LinkedInToolkit
Could not load file or assembly
DotNetOpenAuth version 3.4.7.11039.
Strong name signature could not be
modified....
Considering that the DotNetOpenAuth DLL is delay signed, how to I make my website compile and run?
I've searched web.config and references for any mention of a strongly named DLL. Where else would the strong name check be done?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
![扫码二维码加入Web技术交流群](/public/img/jiaqun_03.jpg)
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
如果您自己编译 DotNetOpenAuth,则应该完全关闭延迟签名,或者将其签名的密钥更改为您拥有私钥的密钥。不要禁用强名称检查——这是一个安全风险。
很好奇为什么你必须编译自己的 DotNetOpenAuth 库。
If you're compiling DotNetOpenAuth yourself, you should either turn off delay signing completely, or change the key it is signed with to one that you have the private key to. Don't disable strong name checking -- that's a security risk.
Curious why you have to compile your own DotNetOpenAuth library though.
您还应该搜索项目引用的引用等,直到找到依赖于
DotNetOpenAuth
程序集签名版本的 DLL。请注意,该程序集可以动态加载,甚至可能不会出现在引用的程序集列表中。您还可以暂时禁用强名称检查,但请确保您意识到可能的情况这样做的后果。You should also search in the references of your project references and so on until you find a DLL which depends on a signed version of the
DotNetOpenAuth
assembly. Note that this assembly could be dynamically loaded and might not even appear in the list of referenced assemblies. You could also disable strong name checking temporary but make sure you realize the possible consequences of this.