Well I really don't have a problem passing things from the VB.NET DLL to blitz. My problems start when I need to pass parameters from blitz to a method in the DLL. Calling methods and returning data to blitz is not a problem. It's when I need to pass parameters _to_ the method the problems start. I'm pretty certain that it's a data type problem. I just can't figure out what. Looking at the IL code I cannot se any obvious faults. There is one thing that worries me though. It seems that the order of the methods in the class gets reversed in the IL code if you use VB.NET as aposed to C#. This shouldn't matter (check the Defiance article above) if you set up the v-Tables correctly. But maybe something else is reversed as well, say paramaters to a function. I can't see it happening, but then I'm not an expert on IL-code.
How did you edit the IL code? I found this yesterday which is kind of helpful when 'un-managing' the .NET DLL (by hacking the IL-code):
ILIDE
It's a simple editor for IL code. It does syntax highlighting and has built in support for de-compiling and compiling (DLL -> IL and IL -> DLL)
Your issues with VB6 probably is another problem, since VB6 is all unmanaged code
I'm going to dig a bit deeper and try to report my findings.
Or maybe there is someone out there that actually has managed to pass parametrs to VB.NET userlibs?
//PetBom
How did you edit the IL code? I found this yesterday which is kind of helpful when 'un-managing' the .NET DLL (by hacking the IL-code):
ILIDE
It's a simple editor for IL code. It does syntax highlighting and has built in support for de-compiling and compiling (DLL -> IL and IL -> DLL)
Your issues with VB6 probably is another problem, since VB6 is all unmanaged code
I'm going to dig a bit deeper and try to report my findings.
Or maybe there is someone out there that actually has managed to pass parametrs to VB.NET userlibs?
//PetBom