How to Use structs in COM interfaces when Automation
compatibility is not an issue?
Answer Posted / 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
VARIANT).
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:
[uuid(21602F40-CC62-11d4-AA2B-00A0CC39CFE0)]
struct MyStruct
{
[helpstring("A long value")]
long nLongValue;
[helpstring("A string")]
BSTR bstrStringValue;
};
// Later in the IDL file
[uuid(...), version(...), helpstring(...)]
library MyLib
{
...
struct MyStruct;
};
For more info see : http://vcfaq.mvps.org/com/4.htm
| Is This Answer Correct ? | 0 Yes | 3 No |
Post New Answer View All Answers
Can I use .net components from com programs?
How to create an instance of the object in COM?
What are queued components?
how to call a dll as a COM dll?
Which namespace do the classes, allowing you to support COM functionality, are located?
What is dcom?
Define and explain about COM?
What is the use of com component in .net?
What is the difference between aggregated and contained objects?
Once I have developed the com wrapper do I have to still register the com in registry?
Suppose we have object b and aggregated object c (in- proc server), created by b. Can you access any interface of b from c? What?s the difference between aggregated and contained objects?
Does .net replace com?
Can you explain what is dcom?
What is reference counting in com?
Is dcom dead?