Communication between 32-bit and 64-bit processes in COM

[TecHNooB]

Anyone know of a good resource that talks about this? If you're familiar with COM, I need to know more about MIDL, specifically how to declare variables that are complex, ie: a struct with pointers to structs with pointers. Need to get these things into 32 bit land and back without heap violations :|

 

[TecHNooB]

http://www.microsoft.com/msj/0898/idl/idl.aspx

^ Great article on IDLs for anyone that cares Should solve my issues as I believe communication between 32 and 64 bit processes should be transparent and my real issue was probably just the general specification of the IDL file.

 

[Cogman]

Good luck. I tried to do a few things with COM a while back, but gave up on it. There simply are not a whole lot of resources on it (especially if you are trying to do stuff with MingW).

 

[Leros]

I recently worked on a software project (very commonly used, probably on your computer ). This system was architected as about 90 separate components that communicated to each other through COM. It was awful.

 

[Crusty]

I recently worked on a software project (very commonly used, probably on your computer ). This system was architected as about 90 separate components that communicated to each other through COM. It was awful.

I've never had an experience as terrible as I did with software and libraries that use COM. I wanted to rip my eyes out daily looking at the monstrosity.

For a quick example, there was one object that had 20 methods on it with the same name and parameters, except each one ended with a different number.

So like Method1, Method2, Method3, Method4, Method5 etc. They would all accomplish the same task in the long run, but each one had different sets of workarounds you had to apply to get it to work properly. Some would be really fast but might cause a segfault, some would be super slow but would always execute correctly.

Programming against moving targets is NOT FUN. D: