Re: Midl Bug with 'call_as'

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Mon, 26 Jun 2006 10:45:58 -0700

Message-ID:

<#dBv7hUmGHA.4076@TK2MSFTNGP05.phx.gbl>

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.