When a DLL is loaded in an application, there are two methods of linking, i.e., Load-time Dynamic
Linking and Run-time Dynamic Linking. Static Linking happens during program development time, where as dynamic linking happens at run time.
Linking and Run-time Dynamic Linking. Static Linking happens during program development time, where as dynamic linking happens at run time.
- Load time Dynamic Linking /Static Linking
In Load-time Dynamic Linking, an application makes explicit calls to exported DLL functions like local functions. To use load-time dynamic linking, a header(.h) file and an import library (.lib) file are provided, while compiling and linking the application. Thus, the linker will provide the system
with information required to load the DLL and resolve the exported DLL function locations at load
time.
- Run-time Dynamic Linking /Dynamic Linking
Dynamic linking implies the process that Windows uses to link a function call of one module to the
actual function in DLL. In Run-time Dynamic Linking, an application calls either the function Load-
Library or the function LoadLibraryEx to load the DLL at run time. After the DLL is successfully
loaded, the function GetProcAddress can be used to obtain the address of the exported DLL
function that has to be called. In case of run-time dynamic linking, an import library file is not
required.
Please note that Tally does not support Static Linking; only Dynamic Linking is possible.
Skip to main content