Linked by Thom Holwerda on Mon 10th Oct 2005 19:27 UTC
Microsoft's phase-out of Visual Basic 6 and move to Visual Basic .Net set up an uproar in the ranks of some of Microsoft's most loyal developers. Earlier this year, several thousand developers, including many Microsoft MVPs (Most Valuable Professionals), signed a petition calling for Microsoft to continue to support VB6. However, enhancements in the VB platform stand to bring some of those people back.
Thread beginning with comment 43068
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
2005-09-13
So the deal with VB is that it is just a sort of declarative means for connecting COM objects to each other. VB and COM are essentially one system, designed specifically to support each other. I'm not very familiar with REALBASIC, but the thing most people complain about when trying to make the switch from VB to VB.NET is the lack of good COM support. You can always build a PIA for wrapping COM objects and interfaces, but marshalling is really not the ideal way to deal with variables, especially complex ones, like recordsets.