CODEWITHSUNDEEP
vb.netreflectionlate-binding
Shimmy Weitzhandler
Shimmy Weitzhandler

Reputation: 104692

vb.net reflection vs. late binding?

What should be more proper or what is recommended to use in VB.NET from either reflection vs. late binding:

'Type can be various objects that have a common property for sure.'
Dim type = sender.GetType()
Dim prop = type.GetProperty("Text", 20)
Dim value = property.GetValue(sender, Nothing)

versus:

Dim value = sender.Text

Upvotes: 1

Views: 1962

Answers (3)

Jules
Jules

Reputation: 4339

If you do use late binding, you can put the method that extracts the properties into a partial class with Option Explicit = Off. That way, you still have type checking in the rest of your code.

Upvotes: 0

Paul Creasey
Paul Creasey

Reputation: 28824

Isn't sender.Text always a string though? So the type of value can be inferred at compile time, making the latter an example of early binding?

Upvotes: 0

Andrew Hare
Andrew Hare

Reputation: 351466

Under the covers they are both doing the same thing (relatively speaking). VB.NET's late-binding feature is done via assembly metadata queries at runtime which is exactly what reflection is all about.

One of the benefits to your first approach is that you have an opportunity to handle errors in a more finely-grained manner.

Upvotes: 1

Related Questions