I'll go out on a limb here and say that it always makes a difference whether
you use Early binding vs late bindging and late binding usually loses the
battle. On the other hand in the context of ADO.NET, you may be talking
about DataBinding controls which is totally different than what is
traditionally referred to by late binding vs early binding. If this is what
you are talking about, AFAIK, then when you set the bindings isn't the
issue - but I think knowing what you are referring to by binding is an
important issue, b/c if you know enough to ask about early vs late binding ,
you probably know why late binding is less attractive.
It's always different. Probably not very well explained but basically :
- Early binding is to know the type of an object at compile time. The
compiler have all the needed element at compile time to build the call into
the excutable code (resolution of calls at compile time)
- With late binding, the type of an object is known only at runtime. It will
need extra instructions to find out where is the method to be called (if it
exists) before calling it (resolution of calls at runtime)
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
