DLL在Windows上搜索
在linux上，为了程序搜索库，我们有 LIBRARY_PATH 和 LD_LIBRARY_PATH 环境变量。我们在Windows上有类似的东西吗？特别是Windows 7？
On linux, we have LIBRARY_PATH and LD_LIBRARY_PATH environment variables in order for programs to search for libraries. Do we have similar thing on windows? Particularly Windows 7?
此外，我想知道DLL使用的最佳实践（在哪里放置，使用envs或不等等），因为我想在Windows上工作每个人都做，而不是为了解决这个问题：）
Also, I would like to know best practices for DLL use (where to put them, use envs or not, etc.), since I want to work on windows like everyone does, and not to sloth myself on workarounds :)
本MSDN文章解释了默认的搜索顺序。我引用：
This MSDN article explains the default search order. I quote:
- 由lpFileName指定的目录。
- 系统目录。使用GetSystemDirectory函数获取此目录的路径。
- 16位系统目录。没有获取此目录的路径的功能，但它被搜索。
- Windows目录。使用GetWindowsDirectory函数获取此目录的路径。
- 当前目录。
- PATH环境变量中列出的目录。请注意，这不包括由App Paths注册表项指定的每个应用程序路径。在计算DLL搜索路径时，App Paths键不被使用。
- The directory specified by lpFileName.
- The system directory. Use the GetSystemDirectory function to get the path of this directory.
- The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched.
- The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.
- The current directory.
- The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. The App Paths key is not used when computing the DLL search path.
在（1）中，如果静态链接到DLL的存根库，我认为lpFileName指定的目录是进程的exe的路径。
In (1), if you statically linked against the DLL's stub library, I think "the directory specified by lpFileName" is the process's exe's path.