Re: PInvoke question (caling conventions of C DLLs)
- From: Tom Shelton <tom_shelton@xxxxxxxxxxx>
- Date: Wed, 14 Nov 2007 16:16:12 -0800
On Nov 14, 5:01 pm, Anonymous <no.re...@xxxxxxxx> wrote:
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?
..NET can support __cdecl functions.
--
Tom Shelton
.
- Follow-Ups:
- Re: PInvoke question (caling conventions of C DLLs)
- From: Anonymous
- Re: PInvoke question (caling conventions of C DLLs)
- References:
- PInvoke question (caling conventions of C DLLs)
- From: Anonymous
- PInvoke question (caling conventions of C DLLs)
- Prev by Date: Re: PInvoke question (caling conventions of C DLLs)
- Next by Date: Re: PInvoke question (caling conventions of C DLLs)
- Previous by thread: Re: PInvoke question (caling conventions of C DLLs)
- Next by thread: Re: PInvoke question (caling conventions of C DLLs)
- Index(es):
Relevant Pages
|