Zorked by MIDL
As in, "You are lost in a maze of twisty passages, all alike."
I'm trying to port some code from a 3rd party OCX up to VC++ .NET 2003. As part of this, I'm fighting through the incompatibilities between mktyplib and the MIDL compiler. If I understood why some of these things were coming out different, I'd have a better shot at fixing them. As it is, I've read the (crappy) Microsoft documentation and find that I'm still in the dark.
On Thursday, Doug gets back from Solutions and -- if this doesn't work -- I get eaten by a grue.
I'm trying to port some code from a 3rd party OCX up to VC++ .NET 2003. As part of this, I'm fighting through the incompatibilities between mktyplib and the MIDL compiler. If I understood why some of these things were coming out different, I'd have a better shot at fixing them. As it is, I've read the (crappy) Microsoft documentation and find that I'm still in the dark.
On Thursday, Doug gets back from Solutions and -- if this doesn't work -- I get eaten by a grue.
no subject
no subject
no subject
no subject
*grin* Aren't friends great?
no subject
"Ding dong, Bill Roper's through, 'et by a grue..."
no subject