.NET DLL Loading from PML Macro in E3D Environment

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?

Top Replies

Parents

Léo SALVADOR 1 month ago
Instead of simply specifying the DLL file name during import, you can use its absolute path.
For example, to import the DLL SampleAssembly.dll located under N:\AVEVA_Tools:
import 'N:\AVEVA_Tools\SampleAssembly'

Make sure not to include the .dll extension at the end, otherwise the path won't be recognized.

In a real scenario, the path would ideally come from an environment variable defined in your launchers.
With the previous example, suppose N:\AVEVA_Tools is stored in the environment variable AVEVA_TOOLS :
!dllPath = !!evar('AVEVA_TOOLS') & '\SampleAssembly' import '$!dllPath'
Cancel
Vote Up +2 Vote Down

Sign in to reply

Cancel
Sambhaji Burungale 1 month ago in reply to Léo SALVADOR

Your solution worked exactly as I needed.

Thank you very much Léo SALVADOR

Really appreciate your help!!
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel

Reply

Sambhaji Burungale 1 month ago in reply to Léo SALVADOR

Your solution worked exactly as I needed.

Thank you very much Léo SALVADOR

Really appreciate your help!!
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel

Children

No Data