Loads a .NET assembly into the .NET Runtime currently executing. Note that you should ensure that any required assemblies and dependent assemblies are loaded explicitly into the runtime.
If the runtime has not been started explicitly it will be launched when this method is called.
System.Core (which includes all the base BCL System libraries contained in
.T. or .F. Always check
.cErrorMsg if result is
The assembly to be loaded. The assembly can be specified in any fo the following ways:
- Using a full or resolved path to the Assembly
You can load an assembly from disk by providing a fully qualified path to the assembly. This works both for signed and unsigned assemblies as long as you know the path. Note that this functionality may not work under some restricted system user policy settings and can be slower than using just the assembly name (see next section), but it is the most common way to load a third party or custom assembly consistently.
*** Full Path oBridge.LoadAssembly("c:\installs\wwhelp\wwRefection20.dll") *** Resolved path via FoxPro SET PATH oBridge.LoadAssembly("wwRefection20.dll") *** Relative Path oBridge.LoadAssembly("..\bin\wwRefection20.dll")
- Fully qualified Assembly Name
This is a fully qualified .NET assembly name which must be used for any Assemblies loaded from the Global Assembly Cache. This syntax must also be used with any local assemblies that are signed.
oBridge.LoadAssembly("System, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b77a5c561934e089")
- Special Names
Several 'high level' names have been set up for commonly used assemblies:
See also:Class wwDotNetBridge
Comment or report problem with topic