The loaded assembly.
Type Reason ArgumentNullException assemblyString is null. ArgumentException assemblyString is equal to string.Empty or starts with the null character ('\0'). System.IO.FileNotFoundException The System.Reflection.Assembly identified by assemblyString was not found. BadImageFormatException The System.Reflection.Assembly identified by assemblyString is not a valid assembly.
System.IO.FileLoadException is thrown if assemblyString specifies the full assembly name, and the first assembly that matches the simple name has a different version, culture, or public key token. The loader does not continue probing for other assemblies that match the simple name.
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 common object file format (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 is 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.
In the .NET Framework version 2.0, processor architecture is added to assembly identity, and can be specified as part of assembly name strings. For example, "ProcessorArchitecture=msil". However, the recommended way to specify an assembly name is to create an System.Reflection.AssemblyName object and pass it to an appropriate overload of the erload:System.Reflection.Assembly.Load method. See AssemblyName.ProcessorArchitecture.