vb.net - option strict question -
Late binding is not allowed and likewise we want it.
Whether our program is running or not on a LAN or on the Internet, we have to slow down an object as one of the two objects. We use that ... if someone is running on LAN or Internet, then use the statement to find out.
When we declare our object in the statement ... then we have declared that we can not use the wrong scope and the object. When we declare it as the 'object' type and if we use a direct seam ... then statement, we get late binding error.
How can we stop this option without dire consequences? / P>
I have not used vb.net - so consider the source but do you have any other type of Can not declare each type as a sub-class, and is there a super class type as the declared type of your object?
Comments
Post a Comment