Alternatives to Using GetProcAddress() With LoadLibrary()

• Microsoft Win32 Application Programming Interface (API) included with:

      - Microsoft Windows NT versions 3.1, 3.5, 3.51, 4.0
      - Microsoft Windows 95 version 4.0
  

SUMMARY

When loading a DLL with LoadLibrary(), an alternative to calling GetProcAddress() for each of your DLL entry points is to have the DLL initialization function initialize a global structure or array containing the addresses of these DLL entry points, then call a DLL function from your executable which will return the address of this structure or array to your executable. You can then call your DLL functions via the function pointers in this structure or array.

MORE INFORMATION

The best place to initialize this structure or array of function pointers would be in the DLL_PROCESS_ATTACH code of your DLL's main entry point. The structure or array containing these function pointers must be declared as either a global variable or as dynamically allocated memory (malloc(), GlobalAlloc(), etc.) in your DLL in order for the executable to be able to address this memory properly.

It is also possible, though not as clean, to export the global structure or array of function pointers so that your executable can use the structure or array by name directly in your executable. For more information on how to declare and export global data in a Win32 DLL, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q90530
   TITLE     : Exporting Data From a DLL

This technique of returning pointers to DLL entry points is a supported technique and will work on all hardware platforms that Windows NT supports.