With Visual Studio, I can see the dll references as the attached picture as an example. With this reference information, I can open the (from the example) Composition project to find all the other references on and on to get all the reference file names.
Is there any utility that does this job automatically? I mean, given an .NET assembly, it checks all the references/dependencies recursively to give the names of DLLs.
I checked cygwin's ldd and Depends.exe, but they don't seem to show the dlls from other projects, but only system dlls.
Load your DLL into it, right click, and chose 'Analyze' - you'll then see a "Depends On" item which will show you all the other dll's (and methods inside those dll's) that it needs.
When a program uses a DLL, an issue that is called dependency may cause the program not to run. When a program uses a DLL, a dependency is created. If another program overwrites and breaks this dependency, the original program may not successfully run.
Dependency Walker (Depends), which can be launched via Process Explorer, no longer works well in Windows 10 as of at least build 10.0. 19043 (21H1 May 2021 update). The UI can hang for several minutes while (e.g.) enumerating Notepad's dependencies. It may be time to have Process Explorer link to an alternative.
Yes: ildasm.exe. It is installed with the SDK.
Should be in a path like: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With