blocks|key|1712180|text|这是我静态链接的原因之一；更大的EXEs，但我以前从来没有遇到过这样的依赖问题。也许这本身就值得一问……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1712181|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This is one of the reasons that I statically link; bigger EXEs but I have never had a dependency issue like this before. Probably worth a question in itself though...

blocks|key|1712208|text|使用Dependency+Walker解决DLL问题要容易得多。它允许您分析应用程序，捕获在启动时加载的DLL和稍后加载的DLL。它会显示出许多与加载DLL或加载失败相关的消息。它还理解DLL的SxS加载。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1712209|您可以将可执行文件作为参数传递给Depends.EXE，它将分析该应用程序。这可以与大多数IDE结合使用。例如，在Visual+Studio中，您可以设置“用于调试的命令”。默认情况下，这是您自己的EXE。将其更改为depends.EXE，并将命令参数设置为(至少)+/pb+your.debug.exe。|offset|length|style|CODE|1712210|entityMap^0|0|3Q|I|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Troublehooting DLL problems is a lot easier with Dependency Walker . It allows you to profile your application, catching both DLLs loaded at startup and DLLs loaded later. It will spit out a lot of messages related to the loading of DLLs, or the failure to load them. It also understands SxS loading of DLLs.

You can pass an EXE as a argument to Depends.EXE, and it will profile that app. This can be combined with most IDEs. For instance, in Visual Studio you can set the "Command for Debugging". By default, that's your own EXE. Change it to depends.EXE, and set the command arguments to (at least) <code>/pb your.debug.exe</code>.

blocks|key|1712256|text|有了同样的问题，我找到了一篇文章，它将我带到VS9.0安装中的debug+DLL。对于默认安装，它们位于：C:\Program+Files\Microsoft+Visual+Studio+9.0\VC\redist\Debug_NonRedist\x86\Microsoft.VC90.DebugCRT。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1712257|有三个DLL和一个清单文件。您可以将这些文件添加到System32目录，将该目录添加到PATH环境变量，或者在调试时将这些文件复制到与可执行文件相同的目录。|1712258|增量链接加快了构建速度(链接器只重新链接已更改的库，而不是重新链接整个项目)。否则，它对构建输出没有任何影响。对于大型项目，我不建议关闭增量链接。|1712259|entityMap^0|1H|2Q|0|P|8|17|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

Having the same problem I found a post that lead me to the debug DLLs in the VS9.0 install. For the default install they were in: <code>C:\Program Files\Microsoft Visual Studio 9.0\VC\redist\Debug_NonRedist\x86\Microsoft.VC90.DebugCRT</code>.

There are three DLLs and a manifest file. You can add these to your <code>System32</code> directory, add the directory to your <code>PATH</code> environment variable or copy the files to same directory as your executable when debugging.

Incremental linking speeds up your builds (the linker only re-links libs that have changed instead of re-linking the entire project). It otherwise has no effect on the build output. For a large project I would not recommend turning off incremental linking.

blocks|key|1712293|text|我有个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1712294|未能加载文件或程序集“AudioInterface，Version=1.0.3548.29920，Culture=neutral，PublicKeyToken=null”或其依赖项之一。此应用程序无法启动，因为应用程序配置不正确。重新安装应用程序可能会解决此问题。(HRESULT异常:+0x800736B1)|1712295|AudioInterface是我的C%2B%2B项目的名称。|1712296|切换到"Release“配置，一切正常。|1712297|我跟踪它到缺少清单文件以及我的DLL，我进一步跟踪到有一个程序集标识集。(属性>清单工具>常规>程序集标识)|1712298|我删除了这个设置，清单放到了正确的位置，一切都正常。|1712299|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I had the problem:

Could not load file or assembly 'AudioInterface, Version=1.0.3548.29920, Culture=neutral, PublicKeyToken=null' or one of its dependencies. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)

AudioInterface was the name of my C++ project.

Switching to "Release" config, everything worked.

I tracked it to lack of the manifest file alongside my DLL, which I further tracked to having an Assembly Identity set. (Properties > Manifest Tool > General > Assembly Identity)

I removed this setting, and the manifest dropped in the right place, and everything worked.

blocks|key|1497367|text|虽然另一个VC9.0项目做得很好，但也有同样的问题。所以我比较了两个项目的设置。关键的区别在于“项目属性”、“->”、“配置属性”、“->”清单工具、“->”输入和输出“->”、“嵌入清单”。此选项必须设置为YES。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1497368|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Had the same problem although another VC9.0 project did well. So I compared both project settings.
The crucial difference was under 'Project Properties' -> 'Configuration Properties' -> 'Manifest Tool' -> 'Input and Output' -> 'Embed Manifest'. This option must be set to YES.

blocks|key|1712440|text|使用function+File->New->Project+From+Existing+Code在VC%2B%2B+2008中重新编译您的项目。这对我自己有帮助，可能对你也有帮助。致以问候。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1712441|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Recompile your project in VC++ 2008 using function File->New->Project From Existing Code.
It helped myself, probably it will help you. Regards.

blocks|key|1497494|text|我遇到了类似的问题，但所描述的解决方案对我来说都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1497495|最后，我执行了以下操作来解决我的问题：|1497496|步骤1:遵循@user176861给出的建议|1497497|第-2步:在VC%2B%2B项目属性->配置属性->链接器->清单文件中:在“其他清单依赖项”中添加以下内容：|1497498|type='win32'+name='Microsoft.VC90.CRT'+version='9.0.21022.8'+processorArchitecture='x86'+publicKeyToken='1fc8b3b9a1e18e3b'|code-block|syntax|javascript|1497499|进行上述更改后，我就可以进行调试了。|1497500|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I faced the similar problem but none of the described solutions worked for me.
Finally I did the following to fix my issue:
Step-1:
Follow the suggestion given by @user176861
Step-2:
In the VC++ Project Properties -&gt; Configuration Properties -&gt; Linker -&gt; Manifest File:
In the &quot;Additional manifest dependencies&quot; add the following:
<pre><code>type='win32' name='Microsoft.VC90.CRT' version='9.0.21022.8' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b'
</code></pre>
After making the above change, I was able to debug.

I have a problem with Visual C++ 2008. I have installed opencv and I've created a new program and I build it with no errors. However, it complains about not finding MSVCR90D.dll when debugging. In release mode there is no problem at all. 

I do have MSVCR90D.dll in one of Winsxs folders. Does anyone know a get-around to this problem? Is this a known bug? 

Gerard

MSVCR90D.dll not found in debug mode with Visual C++ 2008

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在使用Visual C++ 2008时遇到了问题。我已经安装了opencv，并且创建了一个新程序，并且没有错误地构建它。然而，它抱怨在调试时找不到MSVCR90D.dll。在发布模式下完全没有问题。我在一个Winsxs文件夹里有MSVCR90D.dll。有谁知道解决这个问题的办法吗？这是一个已知的bug吗？杰拉德

问在Visual C++ 2008的调试模式下找不到MSVCR90D.dll
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Visual C++ 2008的调试模式下找不到MSVCR90D.dllEN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Visual C++ 2008的调试模式下找不到MSVCR90D.dll
EN