Originally posted by: Nemanja Trifunovic
CoInitialize[Ex] implicitly creates a hidden window with its own message loop, therefore no need for rule 2.
Reply
Originally posted by: Christiaan
Jeff is a good man.. , and I hope it will not end with this two parts. What about Controls that implement "Connection Points" and how does COM manages this within STA, MTA. etc.. Doesn't this sound as a beautfull theme for a "Part III" ?
Christiaan
Originally posted by: Mel
Excellent articles! That's a wealth of information in a neat and concise fashion. Keep up the good work!Have you written on anything else say for example containment & aggregation concepts in COM. If you have, then please let me know. Thanks!
Originally posted by: DanM
Very good!
Reply
Originally posted by: Rachna Chadha
Great.. article...
ReplyOriginally posted by: M.N.V.Sitaram
I've been refering books on COM for the past 1 1/2yrs. This info abt., COM Apts., is really helpful.Thanx and regards to Jeff Prosise.
ReplyOriginally posted by: Sylvain Hamel
I have a com component (exe server) that calls a method of another com component (dll server)
I have a function that uses a parameter LPBYTEBUFFER (standard ms stuff).
When the first component is an sta and second component also my method call is fine. This would be fine except that I cant use connection points that way.
When my first component is free threaded and the other is appartment, the called function receives a busted pointer.
I tried marshalling the Interface pointer using CoMarshallInter... but to no use.
Any hindsight?
ReplyOriginally posted by: fb1
This is the best info i have seen on COM apartments - concise and easy to follow.
Worth reading even if you know how to use the different apartment types, good set of rules to guide newbie's and the pitfalls that we all experience along the way.
Reply