casting [RESOLVED]

[Andy]

ok, so I decided to turn Option Strict On (mainly cause I am now working with C# in addition to VB) and now I have a TON of entries in my Task List. Not surprising. Most of them are simple..cast from a string to an integer or vise-versy. I was wondering though, if explicitly casting, and I mean A LOT of casting is going on now, will be noticable on performance. Particularly, I concerned about the application slowing down due to heavy processing.

Is this a concern? Should I re-structure a data-base table here and there to help prevent this? or does it even matter.

[Briantcva]

Makes you realize how lazy you could get away w/ being in VB doesn't it? Anyway, I'm under the [perhaps mistaken] impression that a cast is going on behind the scenes anyway so it shouldn't slow anything down.

[Pirate]

Late binding does make overhead , so always use always early binding .For casting at runtime , I don't think it would be a big deal.

[Andy]

cool. thanks for the input. I had a LOT of errors to correct. casting to integers, casting to strings, casting controls to textboxes, comboboxes, etc.

now, I have to figure out how to correct the "late binding" errors.