Assembly.LoadFrom Method

Definition

Namespace:

System.Reflection

Assembly:

System.Runtime.dll

Loads an assembly.

Overloads

LoadFrom(String, Byte[], AssemblyHashAlgorithm)	Loads an assembly given its file name or path, hash value, and hash algorithm.
LoadFrom(String)	Loads an assembly given its file name or path.

Remarks

.NET Framework only: See <loadFromRemoteSources> for loading assemblies from remote locations.

LoadFrom(String, Byte[], AssemblyHashAlgorithm)

Source:

Assembly.cs

Loads an assembly given its file name or path, hash value, and hash algorithm.

public:
 static System::Reflection::Assembly ^ LoadFrom(System::String ^ assemblyFile, cli::array <System::Byte> ^ hashValue, System::Configuration::Assemblies::AssemblyHashAlgorithm hashAlgorithm);

public static System.Reflection.Assembly LoadFrom (string assemblyFile, byte[]? hashValue, System.Configuration.Assemblies.AssemblyHashAlgorithm hashAlgorithm);

static member LoadFrom : string * byte[] * System.Configuration.Assemblies.AssemblyHashAlgorithm -> System.Reflection.Assembly

Public Shared Function LoadFrom (assemblyFile As String, hashValue As Byte(), hashAlgorithm As AssemblyHashAlgorithm) As Assembly

Parameters

assemblyFile

String

The name or path of the file that contains the manifest of the assembly.

hashValue

Byte[]

The value of the computed hash code.

hashAlgorithm

AssemblyHashAlgorithm

The hash algorithm used for hashing files and for generating the strong name.

Returns

Assembly

The loaded assembly.

Exceptions

NotSupportedException

.NET Core and .NET 5+ only: In all cases.

ArgumentNullException

assemblyFile is null.

FileNotFoundException

assemblyFile is not found, or the module you are trying to load does not specify a file name extension.

FileLoadException

A file that was found could not be loaded.

-or-

assemblyFile specifies a location that is disabled based on <loadFromRemoteSources>.

BadImageFormatException

assemblyFile is not a valid assembly for the currently loaded runtime; for example, a 32-bit assembly in a 64-bit process.

SecurityException

A codebase that does not start with "file://" was specified without the required WebPermission.

ArgumentException

The assemblyFile parameter is an empty string ("").

PathTooLongException

The assembly name exceeds the system-defined maximum length.

Remarks

This API is not supported in .NET Core/.NET 5+. This method throws NotSupportedException when called. Use LoadFrom(String) instead.

The assemblyFile parameter must refer to a URI without escape characters. This method supplies escape characters for all invalid characters in the URI.

Note

File transfer protocol (FTP) is not supported. If the URI supplied for assemblyFile is an FTP address, the assembly is not loaded. No exception is thrown.

assemblyFile can be absolute or relative to the current directory.

Assemblies can be loaded into one of three contexts, or can be loaded without context:

• The load context contains assemblies found by probing: in the global assembly cache, in a host assembly store if the runtime is hosted, or in the ApplicationBase and PrivateBinPath of the application domain. Most overloads of the Load method load assemblies into this context.

• The load-from context contains assemblies for which the user provided a path that is not included in probing. LoadFrom, CreateInstanceFrom, and ExecuteAssembly are examples of methods that load by path.

  See <loadFromRemoteSources> for loading assemblies from remote locations.

• The reflection-only context contains assemblies loaded with the ReflectionOnlyLoad and ReflectionOnlyLoadFrom methods; code in these contexts cannot be executed.

• If the user generated or found the assembly, it is not in any context. This applies to assemblies loaded using overloads of the Load method that specify a byte array containing an assembly, and to transient dynamic assemblies created with reflection emit and not saved to disk.

The load-from context allows an assembly to be loaded from a path that is not included in probing, and yet allows dependencies on that path to be found and loaded because the path information is maintained by the context.

The LoadFrom method has the following disadvantages. Consider using Load instead.

• If an assembly with the same identity is already loaded, LoadFrom returns the loaded assembly even if a different path was specified.

• If an assembly is loaded with LoadFrom, and later an assembly in the load context attempts to load the same assembly by display name, the load attempt fails. This can occur when an assembly is deserialized.

• If an assembly is loaded with LoadFrom, and the probing path includes an assembly with the same identity but a different location, an InvalidCastException, MissingMethodException, or other unexpected behavior can occur.

• LoadFrom demands FileIOPermissionAccess.Read and FileIOPermissionAccess.PathDiscovery, or WebPermission, on the specified path.

• If a native image exists for assemblyFile, it is not used. The assembly cannot be loaded as domain-neutral.

The assembly is loaded with the evidence that the loader supplies.

LoadFrom(String)

Source:

Assembly.cs

Loads an assembly given its file name or path.

public:
 static System::Reflection::Assembly ^ LoadFrom(System::String ^ assemblyFile);

public static System.Reflection.Assembly LoadFrom (string assemblyFile);

static member LoadFrom : string -> System.Reflection.Assembly

Public Shared Function LoadFrom (assemblyFile As String) As Assembly

Parameters

assemblyFile

String

The name or path of the file that contains the manifest of the assembly.

Returns

Assembly

The loaded assembly.

Exceptions

ArgumentNullException

assemblyFile is null.

FileNotFoundException

assemblyFile is not found, or the module you are trying to load does not specify a filename extension.

FileLoadException

A file that was found could not be loaded.

-or-

.NET Framework only: assemblyFile specifies a location that is disabled based on <loadFromRemoteSources>.

BadImageFormatException

assemblyFile is not a valid assembly for the currently loaded runtime; for example, a 32-bit assembly in a 64-bit process.

SecurityException

A codebase that does not start with "file://" was specified without the required WebPermission.

ArgumentException

The assemblyFile parameter is an empty string ("").

PathTooLongException

The assembly name exceeds the system-defined maximum length.

Examples

The following example loads an assembly given its file name or path.

Assembly^ SampleAssembly;
SampleAssembly = Assembly::LoadFrom( "c:\\Sample.Assembly.dll" );
// Obtain a reference to a method known to exist in assembly.
MethodInfo^ Method = SampleAssembly->GetTypes()[ 0 ]->GetMethod( "Method1" );
// Obtain a reference to the parameters collection of the MethodInfo instance.
array<ParameterInfo^>^ Params = Method->GetParameters();
// Display information about method parameters.
// Param = sParam1
//   Type = System::String
//   Position = 0
//   Optional=False
for each ( ParameterInfo^ Param in Params )
{
   Console::WriteLine( "Param= {0}", Param->Name );
   Console::WriteLine( "  Type= {0}", Param->ParameterType );
   Console::WriteLine( "  Position= {0}", Param->Position );
   Console::WriteLine( "  Optional= {0}", Param->IsOptional );
}

Assembly SampleAssembly;
SampleAssembly = Assembly.LoadFrom("c:\\Sample.Assembly.dll");
// Obtain a reference to a method known to exist in assembly.
MethodInfo Method = SampleAssembly.GetTypes()[0].GetMethod("Method1");
// Obtain a reference to the parameters collection of the MethodInfo instance.
ParameterInfo[] Params = Method.GetParameters();
// Display information about method parameters.
// Param = sParam1
//   Type = System.String
//   Position = 0
//   Optional=False
foreach (ParameterInfo Param in Params)
{
    Console.WriteLine("Param=" + Param.Name.ToString());
    Console.WriteLine("  Type=" + Param.ParameterType.ToString());
    Console.WriteLine("  Position=" + Param.Position.ToString());
    Console.WriteLine("  Optional=" + Param.IsOptional.ToString());
}

Dim SampleAssembly As [Assembly]
SampleAssembly = [Assembly].LoadFrom("c:\Sample.Assembly.dll")
' Obtain a reference to a method known to exist in assembly.
Dim Method As MethodInfo = SampleAssembly.GetTypes()(0).GetMethod("Method1")
' Obtain a reference to the parameters collection of the MethodInfo instance.
Dim Params As ParameterInfo() = Method.GetParameters()
' Display information about method parameters.
' Param = sParam1
'   Type = System.String
'   Position = 0
'   Optional=False
For Each Param As ParameterInfo In Params
    Console.WriteLine(("Param=" + Param.Name.ToString()))
    Console.WriteLine(("  Type=" + Param.ParameterType.ToString()))
    Console.WriteLine(("  Position=" + Param.Position.ToString()))
    Console.WriteLine(("  Optional=" + Param.IsOptional.ToString()))
Next

Remarks

This API is present in .NET Core for compatibility, but it is recommended to use AssemblyLoadContext overloads in .NET Core 2.0 and later.

The assembly is loaded into the default AssemblyLoadContext. For more information on assembly loading, see Managed assembly loading algorithm.

The assemblyFile parameter must refer to a URI without escape characters. This method supplies escape characters for all invalid characters in the URI.

Note

.NET Framework only: File transfer protocol (FTP) is not supported. If the URI supplied for assemblyFile is an FTP address, the assembly is not loaded. No exception is thrown.

assemblyFile may be absolute or relative to the current directory.

.NET Framework only: Assemblies can be loaded into one of three contexts, or can be loaded without context:

• The load context contains assemblies found by probing: in the GAC, in a host assembly store if the runtime is hosted, or in the ApplicationBase and PrivateBinPath of the application domain. Most overloads of the Load method load assemblies into this context.

• The load-from context contains assemblies for which the user provided a path not included in the directories searched by probing. It also allows dependencies on that path to be found and loaded because the path information is maintained by the context. LoadFrom, CreateInstanceFrom, and ExecuteAssembly are examples of methods that load by path.

  See <loadFromRemoteSources> for loading assemblies from remote locations.

• The reflection-only context contains assemblies loaded with the ReflectionOnlyLoad and ReflectionOnlyLoadFrom methods; code in these contexts cannot be executed.

• If the user generated or found the assembly, it is not in any context. This applies to assemblies loaded using overloads of the Load method that specify a byte array containing an assembly, and to transient dynamic assemblies created with reflection emit and not saved to disk.

The LoadFrom method has the following disadvantages. Consider using Load instead.

• If an assembly with the same identity is already loaded in the load-from context, LoadFrom returns the loaded assembly even if a different path was specified.

• An assembly can be loaded in the load-from context even though an assembly with the same identity exists in the load context. Interoperability between the two assemblies will not work, leading to errors such as InvalidCastException, MissingMethodException, or other unexpected behavior.

• Calling LoadFrom with a location that's in the probing path will load the assembly in the load context and not in the load-from context.

• If an assembly file whose identity is goverened by a binding redirect policy is passed to LoadFrom, the policy will be applied and the assembly will be loaded from the probing path in the load context.

• If an assembly is loaded in the load-from context, and later an assembly in the load context attempts to load the same assembly by display name, the load attempt fails. This can occur when an assembly is deserialized.

• LoadFrom demands FileIOPermissionAccess.Read and FileIOPermissionAccess.PathDiscovery, or WebPermission, on the specified path.

• If a native image exists for assemblyFile, it is not used. The assembly cannot be loaded as domain neutral.