This is an antique problem with VB6 DLL and COM objects but I still face it day to day. What tools or procedures can be used to see which DLL file or version another DLL is referencing?
I am referring to compiled DLLs at runtime, not from within VB6 IDE.
It's DLL hell.
Dependency Walker shows you all the files that a DLL links to (or is trying to link to) and it's free.
ProcessExplorer shows you all the DLLs that are currently loaded in a process at a particular moment. This gives you another angle on Dependency Walker which I believe does a static scan and can miss some DLLs that are dynamically loaded on demand. Raymond says that's unavoidable.