I\'m going to give an example of using System.Data.SQLite.DLL which is a mixed assembly with unmanaged code: If I execute this :
var assembly= Assembly.LoadF
The problem is that the CLR does not perform the normal DLL loading steps - like mapping the dlls separate sections into different pages, adjusting fixups, etc. When an assembly is loaded from raw bytes, those raw bytes are mapped into memory as is, and only managed meta-data is read. No amount of evidence or security settings will change this behavior.