Re: CoClass name issues
"George" <George@discussions.microsoft.com> wrote in message
news:85D3633B-0C3A-4913-A56B-97C5C6ABF28A@microsoft.com
Not even those, technically. It would use CLSID and IID.
Then from your point, there is no need from COM client (consumer)
point view to know the so-called interface and Coclass name I
mentioned in my original question #3 and #4, then what is the purpose
of assigning their values?
Well, I bet in your client code you find it easier to deal with symbolic
names than to type in raw GUIDs. Those names appear in the header files
and in the type library. You likely use one or the other when building
your client.
Sorry for my bad description using myself terms. Yes, I mean
OBJECT_ENTRY macros, I think through OBJECT_ENTRY macros, C++ class
name, interface IID and coclass CLSID are binded, correct?
As you can easily establish by looking up the documentation,
OBJECT_ENTRY doesn't mention any IIDs.
--
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