http://blogs.msdn.com/b/jmstall/archive/2007/02/23/managed-native-module-ratio.aspxThere is not always a 1:1 correlation between Managed modules and native modules. For example, Sometimes it's (managed:unmanaged) 1:1. (Normal file-based modules) This is the common case, so people tend to assume it's always true. Regular file-baseden-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/jmstall/archive/2007/02/23/managed-native-module-ratio.aspx#1749832Sat, 24 Feb 2007 02:40:47 GMT91d46819-8472-40ad-a661-2c78acb4018c:1749832Mike Stall - MSFT<p>Mihailik - you're right. Reflection also lets you get the managed modules. I was focusing on out-of-process tool APIs and forgot about the in-process reflection options.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1749832" width="1" height="1">http://blogs.msdn.com/b/jmstall/archive/2007/02/23/managed-native-module-ratio.aspx#1745964Fri, 23 Feb 2007 11:51:39 GMT91d46819-8472-40ad-a661-2c78acb4018c:1745964mihailik<p>AppDomain.GetAssemblies() seems like better alternative than ICorDebug (where that is applicable, of course).</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1745964" width="1" height="1">