I am using import statement to import .NET assembly from PML macro.
import 'TestApp.PMLVisible'
using namespace 'TestApp.PMLVisible'
!!SAGTestInterface = object TestInterface()
!!SAGTestInterface.Launch()
This approach requires DLLs to be co-located with the E3D installation, which restricts portability and centralized management of .NET dependencies. I have requirement to load .NET assemblies which are present in some network folder path.
What are the most robust methods for implementing custom assembly resolution in a PML context? How can we create a flexible, configurable mechanism for specifying DLL search paths?
I tried adding network folder in system PATH environment variable. But it did not work. Any suggestions?