I believe a type library is not mandatory for COM Interop.
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
and a .H file, but no type library. To utilize this interface through COM
Interop from .NET, the description needs to be incorporated into .NET and
a
type library is one of the most obvious ways given the IDL definitions and
ability to incorporate as is in type library or a C++ component that
implements IStorage.
--
Brian R.
"Alexander Nickolov" wrote:
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
a type library. This is _strictly_prohibited_.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Brian R." <8B2H4R_N9G5M3S7@noemail.nospam> wrote in message
news:18EB1AB7-BA44-4419-85CA-2ED9558A89EF@microsoft.com...
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
MIDL tool and that it incorporates the 'call_as' method instead of the
'local'. Given this, is there a midl option that would force it to
pull
in
the 'local' version?
I am trying to use the IStorage::RemoteOpenStream and it is failing on
me.
I cannot get it to work without an exception. I am able to get
IStream::RemoteRead and RemoteWrite to work.
Any help would be greatly appreciated!
--
Brian R.