Assembly.ReflectionOnlyLoad Method (String)
Loads an assembly into the reflection-only context, given its display name.
Assembly: mscorlib (in mscorlib.dll)
assemblyString is a null reference (Nothing in Visual Basic).
assemblyString is an empty string ("").
assemblyString is not found.
assemblyString is found, but cannot be loaded.
assemblyString is not a valid assembly.
Version 2.0 or later of the common language runtime is currently loaded and assemblyString was compiled with a later version.
Dependencies are not automatically loaded into the reflection-only context.
You cannot execute code from an assembly loaded into the reflection-only context. To execute code, the assembly must be loaded into the execution context as well, using the Load method.
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:
Reflecting on executable files compiled in C++ might throw a FileLoadException. 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, specify /fixed:no when you are linking.
The reflection-only context is no different from other contexts. Assemblies that are loaded into the context can be unloaded only by unloading the application domain.
Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.