blocks|key|1753158|text|试试Dependencies+(2019年12月)，它是著名的Dependency+Walker的现代重写(最后一次更新是在2006年)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1753159|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/lucasg/Dependencies|1|http://www.dependencywalker.com/^0|2|C|0|V|H|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Try <a href="https://github.com/lucasg/Dependencies" rel="noreferrer">Dependencies</a> (Dec 2019) which is a modern rewrite of the famous <a href="http://www.dependencywalker.com" rel="noreferrer">Dependency Walker</a> (last update in 2006)

blocks|key|1753374|text|Visual+Studio+tools+(VC\+dumpbin文件夹)中的bin可以在以下位置提供帮助：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1753375|dumpbin+/dependents+your_dll_file.dll|code-block|syntax|javascript|1753376|entityMap^0|P|7|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

<code>dumpbin</code> from Visual Studio tools (VC\bin folder) can help here:

<pre><code>dumpbin /dependents your_dll_file.dll
</code></pre>

blocks|key|1753316|text|最安全的事情是有一些干净的虚拟机，你可以在上面测试你的程序。在您想要测试的每个版本上，将VM恢复到其初始清理值。然后使用它的安装程序安装你的程序，看看它是否工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1753317|Dll问题有不同的方面。如果使用Visual+Studio并动态链接到CRT，则必须分发CRT+DLL。更新您的VS，您必须分发另一个版本的CRT。仅仅检查依赖项是不够的，因为您可能会错过这些依赖项。在干净的机器上完全安装是唯一安全的解决方案，IMO。|1753318|如果你不想建立一个成熟的测试环境并安装Windows7，你可以使用XP模式作为初始的干净机器，并使用XP-More来复制虚拟机。|offset|length|1753319|entityMap|0|LINK|mutability|MUTABLE|url|http://xpmore.codeplex.com/^0|0|0|1E|7|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

The safest thing is have some clean virtual machine, on which you can test your program. On every version you'd like to test, restore the VM to its initial clean value. Then install your program using its setup, and see if it works.

Dll problems have different faces. If you use Visual Studio and dynamically link to the CRT, you have to distribute the CRT DLLs. Update your VS, and you have to distribute another version of the CRT. Just checking dependencies is not enough, as you might miss those. Doing a full install on a clean machine is the only safe solution, IMO.

If you don't want to setup a full-blown test environment and have Windows 7, you can use XP-Mode as the initial clean machine, and <a href="http://xpmore.codeplex.com/" rel="noreferrer">XP-More</a> to duplicate the VM.

blocks|key|1753664|text|在您的开发机器上，您可以执行该程序并运行Sysinternals+Process+Explorer。在下面的窗格中，它将显示已加载的DLL以及指向它们的当前路径，这很方便，原因有很多。如果你正在执行你的部署包，它会暴露出哪些DLL在错误的路径中被引用(即没有正确打包)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1753665|目前，我们公司使用Visual+Studio+Installer项目遍历依赖树，并将程序作为松散文件输出。在VS2013中，这是一个扩展：https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d。然后，我们将这些松散的文件打包到一个更全面的安装程序中，但至少该安装程序会投影所有的.net依赖项，并将它们放入一个点，并在缺少内容时向您发出警告。|1753666|entityMap|0|LINK|mutability|MUTABLE|url|https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx|1|https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d^0|K|T|0|0|1X|2B|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

On your development machine, you can execute the program and run <a href="https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx" rel="nofollow noreferrer">Sysinternals Process Explorer</a>. In the lower pane, it will show you the loaded DLLs and the current paths to them which is handy for a number of reasons. If you are executing off your deployment package, it would reveal which DLLs are referenced in the wrong path (i.e. weren't packaged correctly).

Currently, our company uses Visual Studio Installer projects to walk the dependency tree and output as loose files the program. In VS2013, this is now an extension: <a href="https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d" rel="nofollow noreferrer">https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d</a>. We then package these loose files in a more comprehensive installer but at least that setup project all the dot net dependencies and drops them into the one spot and warns you when things are missing.

blocks|key|1966981|text|在过去(也就是WinXP的日子里)，我常常依赖/依赖于动态链接库依赖遍历(depends.exe)，但有时我仍然无法确定动态链接库的问题。理想情况下，我们希望在运行前通过检查找出问题所在，但如果这不能解决问题(或花费太多时间)，您可以尝试启用http://blogs.msdn.com/b/junfeng/archive/2006/11/20/debugging-loadlibrary-failures.aspx和https://msdn.microsoft.com/en-us/library/windows/hardware/ff556886(v=vs.85).aspx中所述的“加载程序快照”，并简要介绍LoadLibrary+fails;+GetLastError+no+help|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1966982|警告:我以前把我的Windows搞得一团糟，玩gflag把它弄得一团糟，我已经事先警告过你了。|1966983|​|1966984|📷|atomic|1966985|1966986|注意："Loader+snap“是按进程加载的，因此UI+enable不会保持选中状态(使用cdb或glfags+-i)|1966987|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/b/junfeng/archive/2006/11/20/debugging-loadlibrary-failures.aspx|1|https://msdn.microsoft.com/en-us/library/windows/hardware/ff556886(v=vs.85).aspx|2|https://stackoverflow.com/questions/6154600/loadlibrary-fails-getlasterror-no-help/6154709#6154709|3|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/5b5c826cc0545bde39603d65d8d6b4a0.png|imageAlt^0|3D|2E|0|5S|28|1|8I|13|2|0|0|0|0|1|3|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]|$A|19|B|1A|1|1B]|$A|1C|B|1D|1|1E]]|C|$]]|$1|D|3|E|5|6|7|1F|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1G|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1H|8|@]|9|@$A|1I|B|1J|1|1K]]|C|$]]|$1|K|3|G|5|6|7|1L|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1M|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1N|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|W]]|X|$5|Q|R|S|C|$T|Y]]|Z|$5|10|R|11|C|$12|13|14|-4]]]]

In the past (i.e. WinXP days), I used to depend/rely on DLL Dependency Walker (depends.exe) but there are times when I am still not able to determine the DLL issue(s). Ideally, we'd like to find out before runtime by inspections but if that does not resolve it (or taking too much time), you can try enabling the "loader snap" as described on <a href="http://blogs.msdn.com/b/junfeng/archive/2006/11/20/debugging-loadlibrary-failures.aspx" rel="nofollow noreferrer">http://blogs.msdn.com/b/junfeng/archive/2006/11/20/debugging-loadlibrary-failures.aspx</a> and <a href="https://msdn.microsoft.com/en-us/library/windows/hardware/ff556886(v=vs.85).aspx" rel="nofollow noreferrer">https://msdn.microsoft.com/en-us/library/windows/hardware/ff556886(v=vs.85).aspx</a> and briefly mentioned <a href="https://stackoverflow.com/questions/6154600/loadlibrary-fails-getlasterror-no-help/6154709#6154709">LoadLibrary fails; GetLastError no help</a>

WARNING: I've messed up my Windows in the past fooling around with gflag making it crawl to its knees, you have been forewarned.

<img src="https://i.stack.imgur.com/kfCu9.png" alt="enter image description here">

Note: "Loader snap" is per-process so the UI enable won't stay checked (use cdb or glfags -i)

blocks|key|1754042|text|请通过以下链接参阅微软的SysInternal工具包：https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1754043|转到下载文件夹，以管理员权限打开"Procexp64.exe“。打开查找菜单->“查找句柄或动态链接库”选项或Ctrl%2BF快捷方式。|1754044|​|1754045|📷|atomic|1754046|1754047|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/fd6fb9776627a5569877b512cb95245d.png|imageAlt^0|R|20|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|K|3|G|5|6|7|19|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|U|P|V|C|$W|X|Y|-4]]]]

Please refer SysInternal toolkit from Microsoft from below link,
<a href="https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer</a>

Goto the download folder, Open "Procexp64.exe" as admin privilege.
Open Find Menu-> "Find Handle or DLL" option or Ctrl+F shortcut way.

<a href="https://i.stack.imgur.com/FMQyf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/FMQyf.png" alt="enter image description here"></a>

blocks|key|1967864|text|用于查找递归DLL依赖项的I+wrote+a+modern+C%2B%2B+command+line+utility。它易于使用，并输出一个JSON，其中包含有关引用的DLL、DLL加载故障和丢失的DLL的有价值的信息。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1967865|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/BullyWiiPlaza/DLL-Dependencies-Parser^0|6|3|U|3|1U|4|28|3|2C|3|2N|3|D|15|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@$9|10|A|11|1|12]]|E|$]]|$1|F|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

<a href="https://github.com/BullyWiiPlaza/DLL-Dependencies-Parser" rel="nofollow noreferrer">I wrote a modern <code>C++</code> command line utility</a> for finding recursive <code>DLL</code> dependencies. It is easy to use and outputs a <code>JSON</code> with valuable information regarding referenced <code>DLL</code>s, <code>DLL</code> load failures and missing <code>DLL</code>s.

blocks|key|1753130|text|请在谷歌中搜索"depends.exe“，这是一个很小的工具来处理这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1753131|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|$]]

Please search "depends.exe" in google, it's a tiny utility to handle this.

blocks|key|1967330|text|如果你有源代码，你可以使用ndepend。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1967331|http://www.ndepend.com/|offset|length|1967332|它的成本很高，而且比分析依赖项要多得多，所以它可能会对您正在寻找的东西大材小用。|1967333|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|N|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

If you have the source code, you can use ndepend.

<a href="http://www.ndepend.com/" rel="nofollow">http://www.ndepend.com/</a>

It's pricey and does a lot more than analyzing dependencies so it might be overkill for what you are looking for.

blocks|key|1753919|text|.exe项目(https://github.com/brechtsanders/pedeps)有一个命令行工具(copypedeps)，用于复制您的.exe(或.dll)文件以及它所依赖的所有文件。如果您在应用程序工作的系统上执行此操作，则应该能够将其与所有依赖项DLL一起发布。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1753920|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/brechtsanders/pedeps^0|7|13|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The pedeps project (<a href="https://github.com/brechtsanders/pedeps" rel="nofollow noreferrer">https://github.com/brechtsanders/pedeps</a>) has a command line tool (copypedeps) for copying your .exe (or .dll) file(s) along with all the files it depends on.
If you do that on the system where the application works, you should be able to ship it with all it's dependancy DLLs.

blocks|key|1967473|text|如果你的dll是基于.net的，你可以试试JetBrains+dotPeek。这是免费的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1967474|entityMap|0|LINK|mutability|MUTABLE|url|https://www.jetbrains.com/decompiler/download/^0|L|H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If your dll is based on .net you can try <a href="https://www.jetbrains.com/decompiler/download/" rel="nofollow noreferrer">JetBrains dotPeek</a>. It's free.

blocks|key|1967903|text|DLL是否在“调试模式”下编译并部署？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1967904|如果是这样，它可能取决于DLL的"D“版本。例如：|1967905|++MSVCP140D.dll
++VCRUNTIME140D.dll|code-block|syntax|javascript|1967906|如果DLL是在“发布模式”下构建的，则这些不是依赖项。D版本不随Microsoft+Visual+C%2B%2B+Redistributable一起提供。|1967907|看看是不是这样，正如其他人所指出的：|1967908|从Visual+Studio:+Tools+->+Visual+Studio命令提示符。|1967909|在命令提示符下，对DLL运行dumpbin+/dependents。|offset|length|style|CODE|1967910|entityMap^0|0|0|0|0|0|0|E|J|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@$Q|13|R|14|S|T]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

Was the DLL compiled in &quot;Debug Mode&quot; and then deployed?
If so, it may depend on &quot;D&quot; versions of DLLs. For example:
<pre><code> MSVCP140D.dll
 VCRUNTIME140D.dll
</code></pre>
These would not be dependents if the DLL is built in &quot;Release Mode.&quot; The D versions do not come with the Microsoft Visual C++ Redistributables.
To see if that is the case, as others have pointed out:
From Visual Studio: Tools -&gt; Visual Studio Command Prompt.
In the command prompt run <code>dumpbin /dependents</code> against the DLL.

Sometimes when I'm doing a little project I'm not careful enough and accidentally add a dependency for a DLL that I am not aware of. When I ship this program to a friend or other people, "it doesn't work" because "some DLL" is missing. This is of course because the program can find the DLL on my system, but not on theirs.

Is there a way to scan an executable for DLL dependencies or execute the program in a "clean" DLL-free environment for testing to prevent these oops situations?

How to check for DLL dependency?

有时，当我在做一个小项目时，我不够小心，不小心为我不知道的DLL添加了一个依赖项。当我将这个程序发送给朋友或其他人时，“它不工作”，因为“一些DLL”丢失了。当然，这是因为程序可以在我的系统上找到DLL，但不能在他们的系统上找到。有没有一种方法可以扫描可执行文件中的DLL依赖关系，或者在“干净”的无DLL环境中执行程序以进行测试，以防止这些oops情况？

问如何检查DLL依赖关系？
EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何检查DLL依赖关系？EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何检查DLL依赖关系？
EN