Re:Why I am called "the Father of Visual Basic" (1996)
by eterm on Thursday March 19, 2015 @05:10AM
(#9230868)
Professionally it wasn't even that limiting. It handled COM calls OK so you could off load to other libraries if you wanted. I was still developing professionally in VB6 as recently as this time last year (exactly 1 year ago in fact).
While I am extremely glad I got away from VB6, the old dog still had life in her. The main limitation was having to develop in a windows XP virtual machine for better IDE compatability.
By the end we did much of the newer development was in .NET libraries we called from the VB6 front-end, but the front end was still handling most of the data.
While I am extremely glad I got away from VB6, the old dog still had life in her. The main limitation was having to develop in a windows XP virtual machine for better IDE compatability.
By the end we did much of the newer development was in .NET libraries we called from the VB6 front-end, but the front end was still handling most of the data.