msvcp90.dll依赖于错误的msvcr90.dll？
我有一个用 VS2008 (amd64) 构建的 dll 项目。 dll 的清单显示
<assemblyIdentity type='win32' name='Microsoft.VC90.CRT' version='9.0.21022.8' processorArchitecture='amd64' publicKeyToken='1fc8b3b9a1e18e3b' />
当我将 dll 加载到 DependencyWalker 中时，它引用了winsxs-directory
amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251
这是怎么发生的？这整个清单的事情难道不是为了通过向每个 dll/exe 提供其构建版本的信息以及它所依赖的 CRT 版本的信息来避免类似情况吗？
第二，更令人困惑的是，msvcp90.dll依赖于msvcr90.dll，但找不到msvcr90.dll！？！嘿，它与 msvcm90.dll 和 msvcp90.dll 位于同一winsxs目录中！ 如果我将正确的 msvcr90.dll 复制到与我的 dll 相同的目录中，它就可以工作了！ （但是，这不是我们在 DllHell 时代遇到的情况吗？既然我们有清单，那么 msvc*.dll 复制不应该结束吗？？？）
如果有人能为我解释，我将非常感激！
I have a dll project built with VS2008 (amd64). The manifest of the dll say
<assemblyIdentity type='win32' name='Microsoft.VC90.CRT' version='9.0.21022.8' processorArchitecture='amd64' publicKeyToken='1fc8b3b9a1e18e3b' />
When I load the dll into DependencyWalker it refers to winsxs-directory
amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251
How can that happen? Isn't this whole manifest-thing meant to avoid situations like that by giving every dll/exe the information which version it is built with and therefore the CRT-version it depends upon?
And the second, even more confusing thing is that the msvcp90.dll depends on msvcr90.dll but the msvcr90.dll cannot be found!?! Hey, it's in the same winsxs-directory together with msvcm90.dll and msvcp90.dll!
If I copy the right msvcr90.dll in the same directory as my dll it works! (But again, isn't that the situation we had in DllHell times? And shouldn't that msvc*.dll-copying should be over since we have manifests???)
I would be really grateful if anyone has an explanation for me!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
通过清单，Microsft 引入了一种新的“dll 地狱”来解决“dll 地狱”:(
顺便说一句，您引用的最后一个版本 (9.0.30729) 是升级到 SP1 的 MSVCR9 CRT。
也许您可以尝试使用此版本更新 VS2008 以“同步”清单。
With manifest, Microsft had introduced a new kind of "dll hell" to resolve "dll hell" :(
By the way, the last version you are referencing (9.0.30729) is the MSVCR9 CRT upgraded to SP1.
May be you could try to update your VS2008 with this version to "synchronize" the manifest.