BSTR from C Dll to VB
Date: 11.16.20 - 3:29pm
So lets say you have a C function prototype such as the following:
How do you write your API declaration in VB6 to handle this? We all know VB6 deals with BSTRs this should be ok right?
Mmm not really. The Api declare mechanism was written to allow vb6 to interact with standard C dlls. So the runtime does all kinds of automagic translations to meet that expectation.
If your C dll is returning a SysAlloc* BSTR, technically you would need to write a tlb file to include in your VB6.
Ok..so what if you dont want to write and reference a tlb file because they are inconvenient? Can VB6 work with this BSTR anyway?
Now I know what your thinking and the answer is NO. If you try to declare the vb api def with an As String return type, you will get an double unicode string and a leaked BSTR that never gets free'd.
We can however screw with things a little bit and make it work.
If you look at the varptr(s) before it has been set to anything, it value at that address is 0. So VB6 knows it is not a active BSTR and does not need to free it.
This means there is no memory leak if we manually stuff it with a reference to an existing BSTR which no one else owns and no one else will free.
Comments: (1)On 03.23.22 - 2:40pm Dave wrote: