|Midl Bug with 'call_as'||Brian R.||6/26/06 10:18 AM|
I am trying to use IStorage in .NET and the type library that I am importing
the interface definitions from contains a description of OpenStream as
RemoteOpenStream. Using OleView shows that the type lib was constructed with
the RemoteOpenSream method definition instead of the local OpenStream.
I read a short FAQ on the internet that stated that there was a bug in the
I am trying to use the IStorage::RemoteOpenStream and it is failing on me.
Any help would be greatly appreciated!
|Re: Midl Bug with 'call_as'||Alexander Nickolov||6/26/06 10:45 AM|
I wouldn't call it a bug. Simply a type library cannot represent
interfaces with [local]/[call_as] method pairs. This is advanced
IDL well beyond the limited capabilities of a type library...
Your first mistake, however, is putting a standard interface in
"Brian R." <8B2H4R_N9G5M3S7@noemail.nospam> wrote in message
|Re: Midl Bug with 'call_as'||Brian R.||6/27/06 9:56 AM|
I would agree thtat is it undesirable to pull in a standard interface, but we
are having to deal with the fact that .NET has not provided a definition of
the IStorage interface in teh System.Runtime.InteropServices namespace like
it has for UCOMIStream.
As I see it the IStorage interface is a COM interface that provides an IDL
|Re: Midl Bug with 'call_as'||Alexander Nickolov||6/27/06 10:01 PM|
I believe a type library is not mandatory for COM Interop.
Ask in the interop group on how to adapt a non-Automation
interface (that can't be represented in a type library):
"Brian R." <8B2H4R_N9G5M3S7@noemail.nospam> wrote in messagenews:AA40DA62-D573-4875-AF50-280D43EFCCA7@microsoft.com...