• PB Help
  • Application Techniques
    • Program Access Techniques
      • Calling .NET Assembly in an Application
        • About .NET assembly

That section including sub sections on Data types, Classes, and more give you restrictions on current implementation.

Back in the days of SOAP web services I was used to passing complex, nested data structures as serialized XML. These days I use serialized JSON because it is much more compact.

For one of my .NET assemblies I added "interop" classes doing nothing but relaying data between simple data types (more parameters) and complex classes (fewer parameters)

HTH /Michael

Arcady,

This version of the .NET Library importer (and the new DotNetObject object) doesn't support complex data types, either as properties or as arguments to functions. It's documented somewhere in the help. I replicated your scenario and got the same result.

You can view the list of the items that could not be imported by clicking the link "View Failed Items" in the .NET DLL Importer dialog window. 

From my experience, third party libraries tend to offer a simple API to access its functionality, for things like email, ftp, sockets, unit conversion, etc. Nevertheless, I expect Appeon will expand the capabilities of the importer in the future if demand arises.

Regards,

Ricardo

Hi Arcady;

   The .Net "Importer" imposts a .Net "Assembly". Which in turn, can contain multiple classes. Is this what you are trying to do? In other words, are your two classes already in one  .Net assembly together?

Regards ... Chris