Groups | Blog | Home
all groups > dotnet interop > april 2008 >

dotnet interop : Re: COM interface requires Integer in VB, even though INT_PTR is defined in COM interface



theunissen@comcast.net
4/22/2008 8:54:42 AM
Hi,

This message is related to a post I did a few days ago. I had a
problem where INT"_PTR" in a com interface didn't show up as "IntPtr"
inside Visual Basic. This problem was resolved by using a "HANDLE" or
"void*" inside the interface definition in the IDL file. To use the
"HANDLE" definition you should use the "[local]" IDL keyword in front
of the interface or interface function.

The problem I have now is since I changed the interfaces and use the
"[local]" key word it seems I can no longer use these interfaces from
inside a different thread in Visual Basic. Using the interface on tyhe
mainthread is no problem. Is this normal behavior, that once you use
the local keyword, the threading is no longer supported?

AddThis Social Bookmark Button