All Replies

• Friday, September 18, 2009 4:34 AMJon LangdonMSFT, Owner

   
  

  0

  Sign In to Vote

  You're mostly correct, depending on your definition of "source code file" (i.e. IL vs. C#, for example). One file of an assembly is a PE file (a .dll or .exe) which contains the assembly manifest. A module is IL code + associated metadata and can be in the same PE file or exist separately (in the case of a multi-module assembly). Have a look at http://msdn.microsoft.com/en-us/library/zst29sk2(VS.100).aspxfor a more detailed explanation.
  
  Regards,
  Jon

  • Marked As Answer byJon LangdonMSFT, OwnerFriday, September 18, 2009 3:09 PM
  •  
  • Reply
  • Quote

   
• Friday, September 18, 2009 5:50 AMMike Stall - MSFTMSFT

   
  

  0

  Sign In to Vote
  From the ICorDebug perspective, Assemblies contain modules. Modules have all the interesting stuff, like IL and PDBs.
  Some notes from the debugger perspective: http://blogs.msdn.com/jmstall/archive/2006/02/17/modules-vs-assemblies.aspx
  

  ---

  http://blogs.msdn.com/jmstall

  • Marked As Answer byJon LangdonMSFT, OwnerFriday, September 18, 2009 3:09 PM
  •  
  • Reply
  • Quote

   
• Friday, September 18, 2009 11:23 PMlpszDan

   
  

  0

  Sign In to Vote

  Thanks Guys, very much appreciated.
  
  So assembly contains a module. And each module has IL part and Metadata part.
  Does an assembly correspond to a namespace?
  
  I was experimenting with creating assemblies on the fly, that's why I got these questions. I wondered if LoadAssembly will be called when a new assembly is generated from the already running code. Cause I think this is something very powerful to .NET, to be able to just add in memory assemblies. And will it be possible to actually call a function through ICorDebugEval.
  
  How do in-memory assemblies get freed? Does a standard garbage collection mechanism just unload an assembly?