Process Hacker is a very useful tool when exploring Windows Programs.
I have a quick question strictly from a curiosity standpoint. How does Process Hacker enumerate the .NET DLLs loaded by a process? For IIS specifically, I can check out the DLLs loaded by the w3wp.exe process which is the worker thread for IIS and I can see the .NET DLLs loaded. I am not able to reproduce this using the standard procedure of hooking into the process and enumerate the loaded modules. Just curiosity how thats accomplished for a specific project I'm working on.
Thanks for all the help! Cheers