Re: C++ COM STA model
"George" <George@discussions.microsoft.com> wrote in message
news:6EB4E3DE-8B92-432C-B1DF-923ACF909C29@microsoft.com
For IDispatch, you don't need any type lib. Windows ships with a
proxy/stub DLL for IDispatch already installed and registered.
Interested in it. Previously, when I implement IDispatch, I always
write a IDL file and using MIDL compiler to generate a typelib and
register it into Windows Registry, even if it is not dual interface.
When you say "implement IDispatch", do you literally mean you've
implemented GetIdsOfNames and Invoke by hand?
I am interested to learn how to save work of generate typelib. Could
you refer a link or sample please? Could we also save the work of
writing an IDL file?
Well, if you manually implement a pure dispinterface, you simply don't
need to write an IDL file. I'm not sure how I can give you an example of
_not_ doing something.
However, you would probably need to document your interface one way or
the other - otherwise, how would your clients know which methods to call
with what parameters? An IDL description is as good a documentation as
any. And if you write it anyway, you could just as well build a TLB from
it, to make lives of clients easier still.
Well, no, but you still use MIDL compiler to build the type library
(I'm not sure what you mean by "explicitly" here).
I mean manually use MIDL compiler to compile IDL file to generate
stub/proxy files.
Why not just add IDL file to your project? Visual Studio will
automatically run MIDL on it, producing proxy/stub source files and/or
type library.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925