R
RLWA32
Guest
For COM servers created using ATL with VS2015 --
When defining an interface in an IDL file that uses the content of an imported type library the definition must be placed inside the IDL file's library block. For dual interfaces that use automation compatible types this doesn't seem to present a problem. Although MIDL doesn't generate code for a proxy dll the standard marshalling available through the type library is sufficient.
However, let's say that the interface that uses the imported type library is derived from IUnknown and that a proxy dll is needed. Then, the absence of MIDL generated code for a proxy presents a problem.
Is there a way to convince MIDL to generate the missing code?
Continue reading...
When defining an interface in an IDL file that uses the content of an imported type library the definition must be placed inside the IDL file's library block. For dual interfaces that use automation compatible types this doesn't seem to present a problem. Although MIDL doesn't generate code for a proxy dll the standard marshalling available through the type library is sufficient.
However, let's say that the interface that uses the imported type library is derived from IUnknown and that a proxy dll is needed. Then, the absence of MIDL generated code for a proxy presents a problem.
Is there a way to convince MIDL to generate the missing code?
Continue reading...