Bring back Classic Visual Basic, an improved version of VB6
The silent majority of VB6 users did not ask for changes that came with .NET
We request Microsoft brings back classic Visual Basic as COM development is back with Windows 8.
David Platt wrote an excellent article about why classic VB still thrives:
Due to this idea being accidentally declined, we are reverting back to its original status.
We apologize for any inconvenience.
Visual Studio PM
WA Dinam commented
░░░░░███████ ]▄▄▄▄▄▄▄▄ <<<< bring back Visual Basic 6.0
WA Dinam commented
░░░░░███████ ]▄▄▄▄▄▄▄▄ < bring back Visual Basic 6.0 !
vb6 will be very success if microsoft didn't kill it forcibly.
Even erlang can be so success, WhatsApp is developed by erlang,
@Anonymous: Having control arrays is great, but having a way to just connect a routine to the event is just as handy (with that instead of having Index you have Caller (or something like that)), So I really don't mind having that from vb.net (or as I was used to in Delphi), just like really being able to create controls on runtime instead of having to use controlarray's.. But controlarray's are certainly a handy tool (also makes sure you can circumvent some different variable/function name limitations in one project (which they wouldn't have had that in the first place)..
VB releases after VB6 are not compatible with normal usage the way VB needs to be used in a commercial environment. Not having array of controls is exceptionally vexing and makes writing code almost impossible and when you get through, you have more forced connections to routines than code in them. It is ugly and takes a very long time to code. This keeps me on VB6. Need updates without removing so many features like the C coders did to VB Studio after release 6. Horrible idea gone horribly wrong. Bring back a useful version of VB!!!
I dont care much about Syntax difference in VB6 and VB.NET. What i really care about is Compile to Native Code. If Microsoft cant continue the development of VB6 then they should just add a Compile to Native Code Option in VB.NET.
Embarcadero Delphi (formerly Borland/CodeGear) Programming Language was introduced for .NET. The .NET support existed from Delphi 8 through D-2005, D-2006 and D-2007. Later they dropped .NET and reintroduced Delphi which compiles to Native Code and Made another Lang which compiles to .NET called Prism. Another Reason why VB6 should be developed and VB6 & VB.NET can co exists.
hmd far commented
vb6 is my love
Microsoft could easily continue developing VB6 onto VB7 (64/32 bit) and satisfy its userbase.
I can write in 5mn a program in VB6 that would take a C++ programmer hours! I doubt that I am the only one here thugh I cosider myself an "intermediate" developer. With the move to Android platforms etc., VB6 could be made to include new functionality to run such platforms.
For instance I recall using VB6 or similar still: Embedded VB (in 2001), and ended up with an embedded app. in Windows CE within the hour! The app included touch screen and measurment of sensor voltages using ADCs, etc.
Again, nothing special here in fact I had little experience of WinCE.
VB6 brings itself nicely to interface to hardware (Unmanaged development takes care of that!), I have used a commercial portable embedded system with FPGAs etc. where the client software was written in VB6 as of 2003/2004.
In the science field we now get Matlab, LabView etc. These platforms pale away when simple apps are written in VB6. And guess what? many of these vendors now discard development for VB6...
Perhaps it is not fully OOP compliant. But frankly who cares! Many apps hardly need full OOP usage...When you target lean code and speed it is the targetted functionality that is important...
Visual Basic 6.0 CAUSE VB.NET IS FOR *******!
VB6 just had a successful petition to make a 64-bit version on change.org.
Alina S commented
VB6 ┣▇▇▇═─ true VB7
Visual Basic 6.0 ✔
Megan W commented
Dear Visual Studio team (Product Team, Microsoft),
My account is still locked. The message from http://social.msdn.microsoft.com/ is "Your account does not have access to the forums system.".
Thread in forums about Megan's 'unbanning':
Welcome back Megan !
Eugênio Pacelli Salgado Canaan commented
Parabéns ao ADMIN que reviu a situação de Megan
Congratulations to ADMIN who reviewed the situation of Megan.
@MeganWinter, we looked into why you were banned on Forums and you should not have been. We have unbanned you and will further investigate internally as to why this ban took place. We are tremendously sorry and apologize for any inconvenience in which this has caused.
Sanio Montenegro commented
\¸ ♥ VB6 ♥.,.\
Bring back Visual Basic 6.0 !
Winston potgieter commented
@FB Cufar , the reson I posted this, is that it makes a point that non-managed development is making a comeback, and has benefits in todays technology environment. In the last part of the video it shows where dev money was spent and vb6 is included. The whole point is that there is still a need today for a vb6 style dev environment that compiles natively, remember all code written in vb6 compiles via the vc++ compiler.. it interprets the basic syntax and converts it to c++ then compiles. So in essence vb6 produces the same code as vc++.
Bring back vb6, native is cool again for so many reasons, and with an simple syntax like vb6 can be so powerful!