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:
We have read all of the comments on this thread and I’d like to thank you for providing your constructive feedback on this issue. Instead of merely repeating our support and migration guidance that has been laid out on http://msdn.com/vbrun, I’d like to address some of your specific comments here.
To play back the feedback themes we’re hearing:
- VB6 is awesome
- VB6 needs to be brought forward and maintained: in a new release or OSS
VB6 was and still is without a doubt awesome. VB6 made developers incredibly productive building a breadth of applications and as a result we have a wealth of applications and passionate developers to this day in 2014. One way I see our mission in developer tools is to empower developers to solve problems. This includes both today’s problems AND the problems of tomorrow. VB6, as you all have stated repeatedly in this thread, is an excellent tool for solving the problems of its day. We also stand behind our decision starting in 2002 to meet the current demands of our developers and the industry with .NET. For the scenarios VB6 set out to do, we see VB6 being “complete”. We feel good about VB6 being able to continue maintaining their applications for the past 15 years. Current needs ranging from distributed applications and services, to web applications and services, to devices, to new architectures and languages, required fundamental changes to the whole stack. We looked at how we could accommodate these needs through incremental changes to VB6 while maintaining its essence, and that was not possible.
To address the modern needs we would need to go far beyond updating the language. We have to remember that VB6 is not just a language. VB6 is a language, a runtime, a platform library, a tool/IDE, and an ecosystem tightly packaged together in a way that made all of them work well together. We’ve worked with many customers on migration from VB6 to .NET and found that while yes, there are language changes, the dominating factor in migration difficulties isn’t the language differences. Even open sourcing the language/runtime wouldn’t solve the fact that VB6 was thought for a different set of problems, and the fact that its strength came from the end-to-end solution provided by all these five pieces working together. Take a change like 64bit, the complete runtime, tools and ecosystem chain would need to be retooled.
So, moving forward what can we do? Where we have been able to help move forward is in our stance around support and interoperability. The VB6 runtime it is still a component of the Windows operating system and is a component shipped in Windows 8.1. It will be supported at least through 2024. This ensures your apps and components continue to run as you incrementally move forward to .NET. The support policy is here: http://msdn.microsoft.com/en-us/vstudio/ms788708. There are numerous interop strategies that we developed and evolved to enable incremental migration as you upgrade your skills, described here: http://msdn.com/vbrun.
In summary, VB6 was awesome. We agree. We don’t expect or demand anyone to throw away their code or rewrite from any of our technologies unless it makes business sense for them to do so. We have to innovate to enable our customers to innovate. It is not a viable option to create a next version of VB6. We stand by our decision to make VB.NET and the .NET Framework. We think they are awesome too. It is not feasible to open source VB6 tools chain and ecosystem. The VB6 runtime was last shipped in Windows 8.1 and will be supported for the lifetime of Windows 8.1. Support and interop are great tools to move forward incrementally.
I hope you feel we’ve listened to your feedback and that I’ve explained things well enough that you understand our decision.
Group Program Manager
Microsoft Visual Studio Cloud Tools
Bring back Visual Basic
There is a real issue of how to support legacy VB6 applications. Upgrading to VB.net isn't possible for large applications. Yet Microsoft ignores this. Either bring back classic VB6 or open source it.
The Cloud = putting your data on someone elses computer so they can **** it.
I doubt it is possible for VB.net to have full VB6 compatibility.
The best approach is for Microsoft to launch an updated VB6.
Besides fancy people doing fancy things with fancy devices, there is people who spend several hours a day transcribing data. Even after putting all the fancy little gadgets to fancily do most of the work, there are lots of tasks that are best performed using a full size keyboard to type on a large screen. And once you get used to a mouse, it is as good to select and click things as a finger on a touch monitor. With a mouse you may replicate most of the gestures you do with your fingers on a touch screen. Besides, allowing the pointer to rest at some place is also a gesture, which you can't replicate on a touch only device.
There are classes to consume SOAP services from VB6, you may also use the internet transfer control to gain access to sources of information not as structured as SOAP Services, but nevertheless available. You may also POST information to web servers, open connection across dedicated lines, VPNs or the plain internet.
So what are the dreadful limitations of classic VB?
What led someone at MS to dismiss VB6 is probably one of the most stupid, absurd and senseless examples of prejudice in the history of mankind.
"The cloud" is just a heap of information piled up somewhere. At the end, "the cloud" boils down to one end point that answers to requests that comply with a certain protocol: you send bytes, wait for a proper reply, receive bytes and process them. That could as well be done with Fortran or COBOL. That's what computers have always been about, more or less since UNIVAC days.
What is really new is hype dominating common sense and salesmen conducting technicians.
Agree with Leonardo. Internet has been around for 20 years and .Net has been around for 10 years, and today people are still talking about the cloud is the future. Yes it's true, and it will still be the future in the future.
We are asking for a successor of VB6 because VB6 was the world's most popular development tool at the time MS decided to kill it. We need a tool to get thing done easily, rapidly and done well. It will be a success if MS allows VB6 to evolve in the right track.
@Leonardo Azpurua: we are in the same situation - everybody takes about html5 but do not understand that there a also the need for apps with interop (office integration, reporting, drag & drop, keyboard navigation)...
VS 2012 is slow and not a RAD Tool - we small companies need a tool to build apps very quickly - Lightswitch was a good idea but MS has killed the silverlight version which was good for building LOB applications...
Art Gola commented
Die. Die. Die.
Win7 phone break wince, so win7 is dead.
Win8 phone break win7, so win8 phone will be dead too.
Win8 rt break win32 api, so Win8 rt must be dead.
Today, New lanauge has no change to alive, specifically close-source language has no change to alive.If has no mono, .net and c# will die quickly too.
It is not c#, is not the .net framework, not the closed-source language.
So c# and .net has no future if has no mono.
Microsoft has no future is it break compatibility again and again.
Who cares about the future?
Today, I have about 2000 customers using a system written with VB6. Some of them have needed web support for their operations, and I have provided it. Others have requested to go mobile, and I have provided it. Of course, not all has been done with VB6, but the core system is. And it is a fairly large system.
Most of Office Automation is done through COM, which may not be useful in all this new world, but which is still much used for component and programs interoperation within the local computer.
Interop is still needed, and will always be. And breaking COM would mean breaking LOTS of computers.
The future is fine, but they can't break the present and get away with it.
They should know!
i do not understand you .... I too loved vb6 , and vc++ 6 too ....but get over , COM is history and has to go away , future is xaml,cloud,services,wcf not vb6
Uncle Fester's put the Start button back!!
VB6 re-released and bundled with free NSA backdoor API!!!
I can't sign the http://classicvb.org/petition/
But there is another petition at:-
You know, I'm completely agree with an open source version but i'd prefer an updated version by MS. but asking for a new version is just goose chase! so I'll go with Open Source.
Whats keeping you MS? we're waiting!
Microsoft, if you do not understand how stupid about killing vb6 with vb.net, this analogy will make it clear about it. Think about one of your many many genius officer now suggest to kill office by replacing with office.net, which will not backward support the billions of office document files out there in the world, so that the whole world are forced to buy your new office.net ...
Haha, what do you think the actual result will be turned out?!
So, give us back the VB7 we are longing for!
The structure of VB6 should be modified like vb.net and all tools of .net framework and c++ should be added in but in native mod to develop extremely high level application with it
If there is a new version of VB6, not only Visual Basic 6 thrives, Microsoft thrives too!
BASIC: Beginners Are Shafted It's Complicated