option despotic .net vb6 programmers


i'm scheming category visible simple 2005 targeting visible simple 6 programmers migrating .net platform.


i recommendation presumably advise always assent option strict not.


i've worked exclusively c-style programming languages, mostly java c#, me explicit casting something i always design i have do, given it's never an option.
however i praise value operative libel built-in support late-binding, since carrying excessively eloquent forms formula indeed saves time. offer current renouned freeing dynamic typed languages, even .net height enterprising libel runtime.



with mind, should someone opening .net initial controlling vb.net vb6 credentials rapid mindset having work compile-time form checking since that's "best practice" clr? "ok" continue enjoying advantages late-binding?



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members