The assembly is loaded into the domain of the caller using the supplied evidence. The raw bytes representing the symbols for the assembly are also loaded.

Whether certain permissions are granted or not granted to an assembly is based on evidence. The rules for assembly and security evidence merging are as follows:

• When you use a Assembly.Load(string) method with no System.Security.Policy.Evidence parameter, the assembly is loaded with the evidence that the loader supplies.

• When you use a Assembly.Load(string) method with an System.Security.Policy.Evidence parameter, pieces of evidence are merged. Pieces of evidence supplied as an argument to the Assembly.Load(string) method supersede pieces of evidence supplied by the loader.

• When you use a Assembly.Load(string) method overload with a Byte[] parameter to load a COFF image, evidence is inherited from the calling assembly. This applies to the .NET Framework version 1.1 Service Pack 1 (SP1) and subsequent releases.

• When you use a Assembly.Load(string) method with a Byte[] parameter and System.Security.Policy.Evidence to load a COFF image, only the supplied evidence is used. Evidence of the calling assembly and evidence of the COFF image are ignored.

Reflecting on C++ executable files might throw a BadImageFormatException. This is most likely caused by the C++ compiler stripping the relocation addresses or the .reloc section from your executable file. To preserve the .reloc address for your C++ executable file, specify /fixed:no when you are linking.

If you call the Assembly.Load(Byte[], Byte[], System.Security.Policy.Evidence) method more than once on the same assembly but with a different evidence specified, the common language runtime does not throw a System.IO.FileLoadException because the equality and integrity of the different evidence specifications cannot be determined. The evidence that first succeeds is the evidence that is used.

Note that this method overload always creates a new System.Reflection.Assembly object with its own mapping.