VB Calling Convention?!

Hey, im trying to u'ze DLL'z in VB (Just an expierement), I wrote a simple "Hello World" DLL in MSVC++, and tried to call a function from it in VB.

I was hopefull! The Message-Box Popped up. I press'd 'OK', then I got a calling-Convention Runtime error... I've tried like everything, I can't seem to tell VB to u'ze the "cdecl" calling convention, and I don't know wut to tell MSVC++ to compile it with to make VB Happy!

Any idea'z???

Thank'z a LOT for Help! ~SPH :confused: :rolleyes: :confused:

P.S. Here i'z my code!

Here i'z the VB Import Code:

Code:

---


Private Declare Function dllMSG Lib "dll.dll" ()


Private Sub Command1_Click()
    dllMSG

End Sub

---

Here i'z the C/C++/ASM Exported Code:

Code:

---

#include <windows.h>

#ifdef __cplusplus
extern "C"{
#endif//__cplusplus

void __declspec(dllexport) __cdecl dllMSG()
{
        MessageBox(NULL,"VB and C/C++/ASM MIXED!","WOOHOO!",MB_OK);
        return;
}

#ifdef __cplusplus
}
#endif//__cplusplus

---

Think you need to export your functions using __stdcall.

Nope! :p Still not working correctly :p .

Anyone know how 2 do this??? Thank'z 4 any help! SPH

If I remember correctly, you should use the WINAPI calling convention.

I'z the WINAPI Calling convention != '__stdcall'???

Thank'z, SPH :)

In that case, I think it may have something to do with name decoration.

Check your exported function names in the DLL file using QuickView and see whether or not they have an underscore infront.

Are you using a Borland Compiler? If so, Borland & Microsoft don't agree on the naming conventions of __stdcall and __cdecl, but there are ways to resolve this.

A lot of my Q i'z how 2 specify a convention in VB??? :-p!

Thank'z a lot 4 help! :), SPH