//Adapted from a libtool discussion and point out to me by mtemple at wineconf
Windows always loads dll's according to the following
app's load directory
global executable search path
The only two exceptions I know of are:
1) In Win2K and higher, if there is a file called 'app.exe.local' in the same
directory as app.exe, then all dll's will be loaded from the app's load
directory – even if its delay loaded with an absolute path that points
elsewhere. the .local. may also override the 'current directory' part of the
search order listed above, but I'm not sure.
2) You can put something called 'AppPath' in the registry, which will influence
the directories that are searched. I don't know where in the list above that
the directories listed in the 'AppPath' key are inserted.
Being able to do the program.exe.local hack makes it nice to test multiple
versions of the same dll and alway be sure you are using the one you want to