Re: CoClass name issues
"George" <George@discussions.microsoft.com> wrote in message
news:D2BA6814-D819-4F3D-B3EA-2358D64AC2F4@microsoft.com
In ATL wizard (I am using VS 2008) when add a new ATL object, we can
assign 4 names,
1. Short Name (under C++ sub-category);
2. Class Name (under C++ sub-category);
3. CoClass Name (under COM sub-category);
4. Interface Name (under COM sub-category);
My question is how they are binded/related together? My current
understanding is (please feel free to correct and add more points),
Short name is just a root from which other names are derived, by
appending certain prefixes and suffixes. It's not used anywhere beyond
this wizard.
Class name is the name of the class in the generated C++ code.
CoClass name is the name of coclass statement in generated IDL file.
The wizard generates a class implementing one interface. Interface name
is the name of this interface.
- From COM client point of view, it only knows 3 and 4 when create
the class (it knows nothing about real C++ class name defined in 2),
and in the template code generated by ATL, 3 and 4 are binded to 2.
Am I correct? But how it is binded?
I don't understand what you are talking about. The wizard generates a
few text files. The names are mentioned in those text files.
--
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