This DLL must acess Winhttp.DLL, Msxml.DLL and CAPICOM.DLL. Is it possible too?
To take full advantage of this, you "could" make all your calls from functions in the DLL using LoadLibrary(); that way your DLL would always load into the calling process when that process starts even if one or more of the named DLLs is absent. This mght be a good plan if you are planning on distributing the DLL as a standalone product, because now every function called by the user could return an error code for missing import. But this is probably not a good idea if this DLL is part of a larger application... in this case the user would more than likely rather be notified immediately when the program starts that something is missing and the application is not going to be able to do all the things it was designed to do.
FWIW, a handy function for you might be the WinApi "SearchPath" function. It will let you check - without loading - any DLL to see if Windows is going to find it when asked to load it later.
MCM
Leave a comment: