How do I migrate from eVB to Visual Basic .NET?
The move from eVB to Visual Basic .NET is not easy but the benefits of migrating far outweigh the costs: *Richer data types: eVB has only a 16-byte VARIANT; Visual Basic .NET uses the .NET Framework common type system. *Faster execution: eVB is interpreted; Visual Basic .NET is JIT (just in time) compiled to native code prior to execution *Better error handling: eVB only supports “On Error”; Visual Basic .NET supports structured exception handling *Support for structures: not in eVB; Visual Basic .NET supports namespaces, classes, and structures *Object-oriented: eVB is procedural; Visual Basic .NET supports full OOP (object orientated programming) *First-class citizen: eVB is always playing catch-up with MFC; Visual Basic .NET is core .NET *Native XML Support: not in eVB; Visual Basic .NET has native support for XML and XML Web services *Better data model: ADOCE is far surpassed by ADO.NET; our best data model yet *Safer, more reliable execution: eVB is a scripting language; Visual Ba