I have a dll project that creates a com interface in visual studio 2008 on WinXP.
The visual studio idl compiler (7.00.0500) creates the interface header file automatically when compiling.
Trying to load the dll using Loadlibrary() i get error 126 on a Win2000 system (module not found) and 14001 on another XP system (...dont know what to do about this description in MSDN..).
Besides that Loadlibrary() fails, also using regsvr32 for registering the Com object (with the absolute path to the existing dll of course) tells me, that the module could not be found (error 126).
On another XP system, the regsvr32 app throws a messagebox, telling that loadlibrary() function failed, because of something like an "application conflict" (error value = ?)
What to do to make the dll get loaded on different windows OS ?
I assume to deliver several mfc dlls, service packs, or to link statically (create a lib) instead of a dll ?