Rantings of a skinny man..

Thinker: I've done a great deal of different projects with vb.net and never needed to turn Option Strict off. That's not to say I haven't discovered the need to yet :)

Robby:

Visual Basic: 
DirectCast(DirectCast(sender, RadioButton).Tag, String)
 
What about creating instances of classes that you create dynamically
using the CodeDom? Wouldn't you have to declare an Object
variable, and then use the Assembly.CreateInstance method to
initialize it? Wouldn't that be considered late-binding, and therefore,
not supported by Option Strict?
 
You are correct. However, I can see no useful application for this. You could walk the methods of the class using reflection and execute them without late binding if you had to.

In practice if you were compiling class libraries on the fly, you would know a type or interface they would adhere to.

Remember, C# can do virtually everything VB.NET can do and it doesn't support late binding, period.
 
Back
Top