How to determine what DLL\'s a binary depends on using programmatic methods?
To be clear, I am not trying to determine the DLL dependencies of the running exec, bu
That's not possible to determine. At least not without a whole lot of work. Any binary can call LoadLibrary to load a DLL. Even if you were to scan the code for all calls to LoadLibrary, you would have to determine what strings were being used to ID the library. Tracking down where in dynamic memory the string has been placed is going to be harder than you want to tackle.