Re: VB calling DLL only with _stdcall?
- From: Tom Shelton <tom_shelton@xxxxxxxxxxx>
- Date: Mon, 19 Nov 2007 15:44:35 -0800 (PST)
On Nov 19, 3:24 pm, "bpsdg" <bpsdgnewsBR...@xxxxxxxxxx> wrote:
"Michael C" <m...@xxxxxxxxxx> schreef in berichtnews:%23xvZL2uKIHA.3356@xxxxxxxxxxxxxxxxxxxxxxx
"bpsdg" <bpsdgnewsBR...@xxxxxxxxxx> wrote in message
news:%23PigyluKIHA.3356@xxxxxxxxxxxxxxxxxxxxxxx
I'm a fan of dot net but I don't think there is any reason to use it in
this case if your app is all in vb6.
Well, I'm a hobbiest programmer but this app is relativily popular, so I'd
like it to last a few versions longer. I guess that I would have to make the
conversion to vb.net one day or the other.
You know you can mix the two via com interop?
--
Tom Shelton
.
- References:
- VB calling DLL only with _stdcall?
- From: bpsdg
- Re: VB calling DLL only with _stdcall?
- From: Herfried K. Wagner [MVP]
- Re: VB calling DLL only with _stdcall?
- From: bpsdg
- Re: VB calling DLL only with _stdcall?
- From: Michael C
- Re: VB calling DLL only with _stdcall?
- From: bpsdg
- Re: VB calling DLL only with _stdcall?
- From: Michael C
- Re: VB calling DLL only with _stdcall?
- From: bpsdg
- VB calling DLL only with _stdcall?
- Prev by Date: Emailing a form in Visual Basic 2005 Express
- Next by Date: Re: VB calling DLL only with _stdcall?
- Previous by thread: Re: VB calling DLL only with _stdcall?
- Next by thread: Re: VB calling DLL only with _stdcall?
- Index(es):
Relevant Pages
|