Examining an executables dependencies.

Use the Dependency Walker (depends.exe)[^] in command line mode: it does the work you require and send its output to the console. What you need is to spawn its process, attach its output and finally parse what it gives you.

[edit]

After searching a bit on internet, I found these pages:

• http://www.codeguru.com/forum/archive/index.php/t-376151.html[^]
• http://msdn.microsoft.com/en-us/library/ms809762[^]
• http://msdn.microsoft.com/it-it/magazine/cc301805(en-us).aspx[^]

There are some sample code and useful informations about how to do it.

On quick caveat to bear in mind here is that about all you'll be able to work out are the load time or linker supported delay loaded dependencies. If someone's manually loading a DLL then it's a lot harder to detect (although you can get an inkling from the fact that the EXE imports LoadLibrary/GetProcAddress). Things like COM object activation are also hard to track for the same reasons.

Cheers,

Ash

Bleeding Fingers has answered you already on how to do this. But if the executable is currently running, then you may not need to do that and could instead use the EnumProcessModules API function.