As someone who used Visual Basic 1.0 for DOS through Visual Basic 4 (VB5 did not run well on my i80486), I wonder if there is a lot of value in being so compatible with VB6 at this point ? Admittedly I have been out of the VB scene for a while but I assume all the VB6 code that exists doesn't justify this.
Other projects that promise a Visual Basic like RAD experience might be better, such as GAMBAS [0] and vTcl [1].
I feel like this isn't really useful, given that c#, winForms and visual studio community edition is still a really potent combo if you need quick Windows client apps.
I still love whipping up a quick gui once in a while :)
The reason I submitted this is because I know several businesses that still use VB6 programs every day, and a couple software developers who use VB6 nearly every day! (One major accounting package, Sage 500, is written mostly in VB6 too.) While they've made forays into .NET development, "it's just not the same", and a project like this would really be an amazing bridge into the future. Please contribute if you can!
9 comments
[ 3.1 ms ] story [ 29.3 ms ] threadOther projects that promise a Visual Basic like RAD experience might be better, such as GAMBAS [0] and vTcl [1].
[0] http://gambas.sourceforge.net/en/main.html
[1] http://vtcl.sourceforge.net/
I still love whipping up a quick gui once in a while :)