🚀 go-pugleaf

thanks for the quick reply.

>> 1) My dll currently has the most imaginative
>> file name 'hook.dll'. Will I get into trouble when
>> other programs are using the same dll name for
>> their global hook? Or is a unique directory path
>> sufficient?
>
> That depends on 1) where you are placing your DLL, 2) how you are loading
> your DLL (using absolute or relative paths), and 3) how the other programs
> are loading their DLLs.

The exe that installs the hook uses the absolute path although the
DLL is in the same directory (exePath + "\hook.dll"). So I
hope this is safe then.


>> 3) After some tests I needed to change and rebuild
>> my hook dll. However, BCB doesn't link it because of
>> [Linker Fatal Error] Fatal: Could not open D:\...\Hook.dll (program
>> still running?) Using a process explorer I found that two processes
>> still have the dll mapped, iexplorer.exe and dexplorer.exe
>> How can this be after my test program deinstalled the hook?
>
> You can uninstall the hook, but you cannot tell the other processes that
> have the DLL injected into them to release their references to the DLL. 
> You
> can only do that with your own process.  MSDN says as much:

[snip]
thanks for the link!

I found that the referencing IE instance was hanging. That probably
was the reason why all other apps did not reference the DLL anymore
but IE did. After all this seems to be an issue while developing. At
runtime it shouldn't matter who still holds references to the DLL as long as 
the
hook is uninstalled.

Nick