Re: Calling type library dll NOT from project directory
"Alex" <alsim123@hotmail.com> wrote in message
news:1184612224.676251.144870@k79g2000hse.googlegroups.com...
David, you are exactly right and reasonable - if you have to implement
some SDK, you can expect exactly what you mentioned above. But in
real life sometime you have to deal with bad designs and decision (or
I'm suspecting this SDK is really old). So, as I mentioned in my post
#4, the only way I can implement this SDK is explicit linking. This
means a lot of extra typing, but nothing I can do about it. At least
this way these SDK functions work properly. And answering your
question about the deployment of my application you were right - my
exe can be run only on the machine where the "main product" which this
SDK was created for, has been installed. So somewhere there will be
this dll (the path to it I will be able to read from the registry).
It cannot be run on a "clean" machine.
Yes, if this is the (sad) case, you are right the only way you can specify
the DLL path is to use LoadLibrary().
-- David