PInvoke question (caling conventions of C DLLs)
- From: Anonymous <no.reply@xxxxxxxx>
- Date: Thu, 15 Nov 2007 00:01:55 +0000
I want to call functions in a Win32 DLL from VB. The DLL in question, is the Python DLL (python25.dll).
I have noticed something strange. When I declare the functions in VB6 (i.e. VB classic), I get an error : "Bad DLL calling convention" - yet when I run the same code through VB.Net, the code works fine - my assumption is that VB.Net can make calls to C functions using either the __stdcall OR __cdecl, whereas VB6 requires the __stdcall calling convention.
This is just a hunch - does anyone know the technical reason for this behaviour?
.
- Follow-Ups:
- Re: PInvoke question (caling conventions of C DLLs)
- From: Tom Shelton
- Re: PInvoke question (caling conventions of C DLLs)
- From: Armin Zingler
- Re: PInvoke question (caling conventions of C DLLs)
- Prev by Date: Re: Off Topic possibly
- Next by Date: Re: PInvoke question (caling conventions of C DLLs)
- Previous by thread: Threading won't work on a function with parameters
- Next by thread: Re: PInvoke question (caling conventions of C DLLs)
- Index(es):
Relevant Pages
|