4 ms·
To be fair, DLL Hell has a lot more issues than just versioning or registering the unload handler. First, there’s load order which can mean that you’re not act
by inlined 7y ago
To be fair, DLL Hell has a lot more issues than just versioning or registering the unload handler.
First, there’s load order which can mean that you’re not actually loading the DLL you think you are.
The second is WOW64 (Windows on Windows). Rather than using fat binaries like Linux and Mac OS, Microsoft decided to use a “brilliant” strategy where the file system lies to you in the “right” ways so that old 32-bit folders are moved to new addresses and the old 32-bit named golfers hold 64-bit binaries. This means that unless you use the “I really mean it” escape mechanisms (e.g. the “sysnative” directory) 32-bit binaries on 64-bit windows is actually loading DLLs from different paths than the code says.