There is a cool life-hack that I learned from my colleague: you associate .dll files with Dependency Walker, and now whenever you try to "run" a .dll file, it opens Dependency Walker for its analysis.
The problem is that there are two version of Dependency Walker: one 32-bit and another 64-bit. And it is recommended to use version of the same bitness for a .dll:
Yes. Dependency Walker will work with any 32-bit or 64-bit Windows module. There are 32-bit and 64-bit versions Dependency Walker. All versions are capable or opening 32-bit and 64-bit modules. However, there are major advantages to using the 32-bit Dependency Walker to process 32-bit modules and the 64-bit Dependency Walker to process 64-bit modules. This is especially true when running on a 64-bit version of Windows, which allows execution of both 32-bit and 64-bit programs. The 32-bit subsystem on 64-bit Windows (known as "WOW64") has its own private registry, "AppPaths", "KnownDlls", system folders, and manifest processing. Only the 32-bit version of Dependency Walker can access this 32-bit environment, which is needed to accurately process a 32-bit module. Likewise, only the 64-bit version of Dependency Walker can fully access the 64-bit environment, so it should always be used for processing 64-bit modules.
Is there a way to associate 32-bit dlls with 32-bit version of Dependency Walker and 64-bit dlls with 64-bit version of Dependency Walker? I'm particularly interested in answer for Windows 7 or 10.