For a C++ custom object loaded by the proxy, the returned value will be the directory where the custom DLL was loaded from. If the custom object was created by the application, the returned value will be an empty string.

For a .NET custom object, regardless of how it was created, this will be the directory of the assembly where the custom object type is defined.

For a Java custom object, regardless of how it was created, this will be the directory of the class file or jar file where the custom type is defined.

For a C++ custom object loaded by the proxy, the returned value will be the directory where the custom DLL was loaded from. If the custom object was created by the application, the returned value will be an empty string.

For a .NET custom object, regardless of how it was created, this will be the directory of the assembly where the custom object type is defined.

For a Java custom object, regardless of how it was created, this will be the directory of the class file or jar file where the custom type is defined.

For a C++ custom object loaded by the proxy, the returned value will be the directory where the custom DLL was loaded from. If the custom object was created by the application, the returned value will be an empty string.

For a .NET custom object, regardless of how it was created, this will be the directory of the assembly where the custom object type is defined.

For a Java custom object, regardless of how it was created, this will be the directory of the class file or jar file where the custom type is defined.