Re: Fixed array as out parameter in DCOM
Surely DCOM doesn't require automation interfaces, and
surely you can marshal fixed arrays via standard marshaling!
I suspect you confuse standard marshaling (via a proxy/stub
DLL) with Automation marshaling (via the IDispatch marshaler
with help from a type library) which is merely a specialized
case of standard marshaling.
Egbert, with all due respect, please refrain from posting
guesses.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Egbert Nierop (MVP for IIS)" <egbert_nierop@nospam.invalid> wrote in
message news:7E8B9CAA-604B-465A-A3A4-0340037B505C@microsoft.com...
"jonathannah" <jonathannah@discussions.microsoft.com> wrote in message
news:7CA44790-EE6B-406D-9459-673FBF8CA50E@microsoft.com...
I do have a proxy/stub for the interface. There is no library block in
the
IDL, and the iface is not dual or oleautomation.
As I said, on the verver side, I see the arrays getting populated, but
when
I return to the client, the arrays are zero'd (I call ZeroMemory befor
ecalling the interface method).
If you want DCOM to automatically marshall data, you can't get away with
fixed length byte arrays. Then you'll need custom marshalling.
To be sure that DCOM supports it, you must mark the interface for
oleautomation. IDL will tell you if something is legal or not :)