How to Use structs in COM interfaces when Automation
compatibility is not an issue?
Answer / krishna akkulu
Structs, also known as User Defined Types (UDTs), can be
used in Automation- compatible interfaces
An Automation- compatible struct may contain only primitive
Automation types as its members.
Nesting structs is not allowed, but VARIANT is allowed thus
enabling nested structs (you can store a struct in a
In order for a struct to be usable for Automation-
compatible interfaces, the struct must be described in a
type library and it must be declared with its own GUID:
[helpstring("A long value")]
// Later in the IDL file
[uuid(...), version(...), helpstring(...)]
For more info see : http://vcfaq.mvps.org/com/4.htm
|Is This Answer Correct ?||0 Yes||3 No|
C is aggregated by B, which in turn aggregated by A. Our client requested C. What will happen?
Which namespace do the classes, allowing you to support COM functionality, are located?
Write a JCL to copy only selected members from a partitioned data set to another partitioned data set. (Use: IEBCOPY)
what is oops
How to Use structs in COM interfaces when Automation compatibility is not an issue?
What are the purposes of AddRef, Release and QueryInterface functions
What is IUnknown? What methods are provided by IUnknown?
What should QueryInterface functions do if requested object was not found?
Explain object pooling?
Differentiate normal DLL to COM DLL
how do you know it is general dll or com dll
What is the difference, if any, between OLE and COM?