vb.net - Late Binding in VB -

from have read far, late binding defining variable object , assigning actual object later done @ run time. don't understand point that. maybe java in me, doesn't limit functionality in object? saying, "i want potential of stuff, don't want have access it." there actual purpose late binding in vb, or java matter, i'm overlooking?

you have backwards. using binding limiting members of type of variable. option strict on, variable declared type object allow access members of type object, regardless of type of object refers to. option strict off, can access member of name on variable of type object , compiler won't complain. it's @ run time type checking done so, long actual object assigned variable has member name, code run.

probably common use late binding office automation. there other options but, in past, if referenced office library , used specific types contained, facilitating binding, limited specific version of office. in order support multiple versions, had forgo reference, declare variables type object , use late binding. long version of office present @ run time included specified members on objects used, code run without issue.

by way, late binding doesn't require using type object, although common. means reference less derived type object , use member of object's type reference's type doesn't have, e.g. use type control , use member specific type button.