Thanks a lot b32 for your post.
As a matter of fact, your solution (the dll method returning a string with all the values separated by a # character and then parsing the string and filling the type fields at the Blitz side) is what we are using right now as a temporary solution. Nevertheless, we hoped that someone could have experienced the same strange thing and maybe knew how to resolve it. It looks like we will be adopting the string solution as a permanent solution, though. :-)
BTW, we also tried without the type fields and the exception still occurs.
I agree with you about the problem being at the C# side. I am pretty sure if the dll was written in C++ this wouldn't be hapening. The .NET way to manage (or unmanage) some things like pointers and references, really creeps my nerves!
Thanks again for your post.
As a matter of fact, your solution (the dll method returning a string with all the values separated by a # character and then parsing the string and filling the type fields at the Blitz side) is what we are using right now as a temporary solution. Nevertheless, we hoped that someone could have experienced the same strange thing and maybe knew how to resolve it. It looks like we will be adopting the string solution as a permanent solution, though. :-)
BTW, we also tried without the type fields and the exception still occurs.
I agree with you about the problem being at the C# side. I am pretty sure if the dll was written in C++ this wouldn't be hapening. The .NET way to manage (or unmanage) some things like pointers and references, really creeps my nerves!
Thanks again for your post.