> And there aren't that many breaking changes between VB6 and VB.net. If you just count syntax, maybe. But the entire environment and API of VB6 wasn't there,

> And there aren't that many breaking changes between VB6 and VB.net. If you just count syntax, maybe. But the entire environment and API of VB6 wasn't there, making the transition pointless. It's like arguing that Windows C programmers have an easy transition to C on Linux because it's the same language. VB.Net in it's current form should never have existed. VB.Net should have been able to run VB6 applications unmodified giving a straight forward transition from VB/VBA to .Net. Instead most apps were never ported from VB6 and VBA. It was a huge missed opportunity.