Late Binding

Late Binding Why? You should always use early binding which will give you the best performance and you will have the compiler available to you for syntax checking and runtime errors, also IntelliSense. But you may consider late binding if you have the following condition(s). Having to work with unmanaged code for example, Com Objects Having to work with many third-party class libraries that change frequently Including ActiveX Controls Having to work on large and complicated software projects where you have many developers and companies involved Working with many different languages for example Python, Rubio, PHP and VFP. There are many more languages that can be incorporated. Especially when working on cross-platform mobile applications

What Is Late Binding? Late binding, or dynamic binding,  is a computer programming mechanism in which the method being called upon an object or the function being called with arguments is looked up by name at runtime. With early binding, or static binding, in an object-oriented language, the compilation phase fixes all types of variables and expressions. This is usually stored in the compiled program as an offset in a virtual method table (“v-table”) and is very efficient. With late binding the compiler does not have enough information to verify the method even exists, let alone bind to its particular slot on the v-table. Instead the method is looked up by name at runtime. The primary advantage of using late binding in Component Object Model (COM) programming is that it does not require the compiler to reference the libraries that contain the object at compile time. This makes the compilation process more resistant to version conflicts, in which the class’s v-table may be accidentally modified. (This is not a concern in JIT-compiled platforms such as .NET or Java, because the v-table is created at runtime by the virtual machine against the libraries as they are being loaded into the running application). Reference source: Wikipedia, the free encyclopedia