quote:
Originally posted by Mnjul
Well Choli, it seems that you haven't searched whole MSDN and Microsoft KB...
lol,
can you give me the link where you found that, please?
quote:
Originally posted by Mnjul
Would this work?
yes and no, dodgy things are happening here... err... I mean:
When in VB (btw, VB 6, not .net) I put the CDecl keywork, VB recognices it (yay!
) but I've found this things: I call the function in the DLL and when I put the CDelc, VB says wrong calling convention and if i remove CDecl it works. That was a quick test, so I said, I'll repeat later. Now, I've exported 2 functions, one with __cdecl and the other with __stdcall. If un VB I use the CDecl I can't call the function with __stdcall but I can call it if don't use CDecl (
), but I can't call the __cdecl using nor not using CDecl
Also, if in VC++ I export a function without saying __cdecl nor __stdcall, I can't call it from VB either (the default setting at the VC++ proyect is __cdecl).
So I'm starting to be paranoid
Once the DLL is built, how can I know the calling convention of an exported function (with the dependency walker I can see the exported functions, but not their calling convention).
I'm using VC++ .NET 2002, if that helps
I'm sure I'm doing something wrong but it seems I missed it
Well, thanks a lot for your help... After seeing how VB compiles the code with the CDecl keyword I'm sure that doing that is possible... Definetely I have to do more tests
/ 
