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.
Your first mistake, however, is putting a standard interface in
a type library. This is _strictly_prohibited_.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnic...@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Brian R." <8B2H4R_...@noemail.nospam> wrote in message
news:18EB1AB7-BA44-4419...@microsoft.com...
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.
microsoft.public.dotnet.framework.interop
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnic...@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Brian R." <8B2H4R_...@noemail.nospam> wrote in message
news:AA40DA62-D573-4875...@microsoft.com...