handling ref and out parameters in .NET functions.

[kinsung]

In the project, there is no class that can handle the passing of function parameters as 'out' or 'ref' parameter objects. When using pointers in C++, the application crashes upon calling the function.

[Th3T3chn0G1t]

@kinsung The current recommended usage is to use pointers w/ unsafe blocks on the C# side to pass any type not directly supported by the Coral type interface. This helps circumvent apparent calling convention issues when passing non-trivial objects across the managed boundary.

I will update you if this changes but atm it appears to be a .NET embedding issue. If you could try using pointers on both sides of the boundary does that solve your problem/usecase?