The following list describes the application criteria for choosing between load-time dynamic linking and runtime dynamic linking −

When you use runtime dynamic linking, you do not need an import library file. After the DLL is successfully loaded, you use the GetProcAddress function, to obtain the address of the exported DLL function that you want to call. In runtime dynamic linking, an application calls either the LoadLibrary function or the LoadLibraryEx function to load the DLL at runtime. When you do this, the linker will provide the system with the information that is required to load the DLL and resolve the exported DLL function locations at load time. To use load-time dynamic linking, provide a header (.h) file and an import library (.lib) file, when you compile and link the application. In load-time dynamic linking, an application makes explicit calls to the exported DLL functions like local functions. When you load a DLL in an application, two methods of linking let you call the exported DLL functions. First, we will discuss the issues and the requirements that you should consider while developing your own DLLs.

What is a dll file?