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
Jean #Support VB6 programming commented
Microsoft say "Microsoft is committed to support existing Visual Basic 6.0 applications that run on Windows Vista, Windows Server 2008 including R2, Windows 7, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows 8.x, and Windows 10"
That's really all we need.
VB6 will last forever.
Retired Coder commented
I don't know if something is wrong but Tiobe has shown VB6 falling off a cliff since January:
"Today VB6 continues to cut a path to working apps, eroding its way through new obstacles, as the Mississippi River cuts new pathways through its delta to the sea, even as the silt it carries clogs the old ones. Like Ol’ Man River, VB6 just keeps rollin’ along."
VB6 programming will outlive .Net.
"With these latest improvements to compatibility, I foresee at least another ten years of life for VB6. And I’ll bet you anything that this support gets renewed in Windows 11 and 12, or whatever they’re called by then. Another decade of driving the puritans crazy. I can dig it."
VB6 programming will outlive .Net.
vb6 is different flavor. true rapid application development tool. why scrapping which is so favorite with developers. do you think you know better than your customers what they want.
Is something wrong with Tiobe? It has VB6 down to 20th place and VB.Net at 5th place. No way can that be right. Nobody uses VB.Net!
Top 10 languages for Enterprise Application Development.
C++ ................ 46%
Python ............ 25%
Visual Basic 6 ..16%
The latest release of the utility to install the VB6 programming IDE on Windows 7 and Windows 10 is available here...
Visual Studio 6.0 Installer wizard v.5.0
This release has been tested on Windows 10 v1803
The Microsoft support statement for VB6 programming is available here...
Support Statement for Visual Basic 6.0 on Windows
- Note: The support policy below has been updated with Windows 10 version 1709 support information.
The Visual Basic team is committed to "It Just Works" compatibility for Visual Basic 6.0 applications on the following supported Windows operating systems:
Windows Server 2016
Windows Server 2012 including R2
Windows Server 2008 including R2
The Visual Basic team’s goal is that Visual Basic 6.0 applications continue to run on supported Windows versions.
As detailed in this document, the core Visual Basic 6.0 runtime will be supported for the full lifetime of supported Windows versions, which is five years of mainstream support followed by five years of extended support.
The VB6 runtime will ship and will be supported in Windows 10 for the lifetime of the OS (that is until at least 2025).
The VB6 runtime will ship and will be supported in Windows Server 2016 for the lifetime of the OS (that is until at least 2027).
Microsoft say "Microsoft is committed to support existing Visual Basic 6.0 applications that run on Windows Vista, Windows Server 2008 including R2, Windows 7, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows 8.x, and Windows 10."
Stack Overflow CEO Joel Spolsky, describes VB6 programming as "the most perfect programming environment ever created."
VB6 - the most perfect programming environment ever created.
>> VB.Net was never needed or wanted. It does nothing that C# can't.
>> An updated VB6 programming language would have been widely adopted.
>> Microsoft got it wrong.
Microsoft got it wrong, AGAIN.
>> You can only wonder what the story would have been had Microsoft offered C# (a fine language, despite its detractors) together with an updated VB6 language (instead of VB.Net).
VB.Net was never needed or wanted. It does nothing that C# can't.
An updated VB6 programming language would have been widely adopted.
Microsoft got it wrong.
VB6 programming and VBA programming will continue as long as Windows exists. One day Microsoft will realize this.
>> can you believe this! 15 years after support was discontinued..
>> By not offering an upgrade path for VB6 Microsoft condemned VB.Net (and by extension C#) to failure. No one could trust Microsoft again.
>> One of the reasons VB6 programming remains popular is as Dan Appleman said 'I think it’s pretty clear that anyone who has thousands of lines of code invested in VB6 is probably not going to invest in porting. It simply isn’t worth it - pure cost, and probably no improved performance.'
And yet Microsoft still don't get it.
They still think the answer is to "incrementally move forward to .NET."
It isn't going to happen. VB6 will still be around when Microsoft abandon .Net.
VB6 +VB.Net +VBA = 48%
VB6 +VBA = 31%
C# = 26%
VB is more used than C#