Late Binding?

[cpatzer]

Hello all,

I tried making my application with Option Strict On. Arg!! I understand the implicit conversion errors and functions that have to have their return type declared, but what is it with late binding? I can't declare a variable of type [some object type] and then assign an object to it? That seems really stupid.

Lets say I try to do this:

Dim item As ListViewItem
            item = sender.GetItemAt(e.X, e.Y)

I tried making it work like this:

Dim item As ListViewItem = sender.GetItemAt(e.X, e.Y)

How could I do what I am trying to do with Option Strict On?

Thanks.

[Aaron Young]

Presumably you're executing this code in an Event, so Sender is of type Object.
To support Option Strict you need to cast the sender variable to a ListView, i.e.

Dim item As ListViewItem = CType(sender, ListView).GetItemAt(e.X, e.Y)

Regards,

- Aaron.

[cpatzer]

Once again. Thank you Aaron!

[taxes]

Hi,

FYI DirectCast is substantially faster than CType. Convert. is slightly faster again but is not applicable to your requirement.

[DWRoelands]

FYI DirectCast is substantially faster than CType. Convert. is slightly faster again but is not applicable to your requirement

I was under the impression that CType was faster than Convert because CType is compliled inline whereas Convert requires a function call.

[cpatzer]

I would be very interested in seeing which is faster. Any body want to run some tests?

[taxes]

Hi,

Tests have been posted in at least one other thread. DirectCast is 4 or 5 times faster than CType. Convert, when you can use it, is 5% faster than DirectCast.

have a look at

http://www.vbforums.com/showthread.p...ght=DirectCast

It really is a question of horses for courses.