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:
VB 6.0 should have never been put out to pasture. I see it as the underlying language in lots of applications from accounting packages to point of sale systems, astronomy to music production. It's at the heart of a couple radio station automation programs, and is used even in the storage space rental industry!
But VB 6.0 needs to be ported cross-platform so it can live with Linux servers, Mac, etc.
Even at this late date I still write apps in VB 6.0 because it's a snap to prototype. I also like the "backwards design" that is, writing from the interface backwards. This is probably why VB 6.0 apps are so user friendly.
There a lot of votes for a "improved" version of VB6. Which I think won't happen. So why don't Microsoft release vb6 compiler source code as Open Source?
Then if a third party or company want to continue develop and maintain "vb6" they can.
Our voices are united and we unanimously wish the return of Visual Basic 6.0 to the market !
Dear Microsoft, we still love you, but when will you get the point regarding VB6:
Dear brothers of the programming community, for those who see this message, please vote here:
Please, Microsoft, post an answer to http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221 .
Thank you! Markus Melk
Since Microsoft has abandoned your most successful development language vb6 decade. But a lot of the old professional programmers are still using vb6, Can Microsoft send VB6 as a gift to these old programmer? Perhaps these old programmers can make VB6 run on the Window8 and Windows Phones. .NET is really too slow and too complicated.
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
Please, add VB6 support in next Visual Basic 14.
Would LOVE for Microsoft to bring back VB6!
Updated VB6 should come back. I 'm in the Developer Business for 16 years and I heard many voices that it should come back. One thing Microsoft should understand, there are (like me) many unrepresented / untold VB6 lovers exists. Please reconsider.
1600 posts and 7433 votes. Yet Microsoft ignore their customer's views in this appeal for VB6 programming.
i use vb6 and very very like it
Interesting poll "What programming language changed your life ?"
Nobody selected VB.Net.
C# is top. But BASIC and VB6 programming added together would have topped the poll.
The article describing how to install the VB6 IDE on Windows 7 has now had over 400,000 views.
and the similar article for Windows 8 has almost 51,000 views.
And with Microsoft support until 'at least' 2024, VB6 programming and VBA programming continues.
VB6 programming on Windows 10:-
How to install the VB6 IDE on Windows 10 technical preview
With Windows 10 less than 12 months away it's good to know that the VB6 programming language continues.
Yes - if MS doesn't want to update it, then our second appeal is to open source it! Look here: http://facebook.com/video.php?v=773460922696660
Yes, as Microsoft ease .Net into open source you have to wonder why they won't do the same for the VB6 programming language.
Yet Microsoft say " It is not feasible to open source VB6 tools chain and ecosystem."
You have to wonder why it is feasible for .Net but not for VB6 programming.
"If Microsoft doesn't want it and lots of other people do, why not?" - seems such a simple question, but not one Microsoft are likely to answer.
Jeff ray commented
So, since Microsoft is completely abandoning VB6, why don't they release it to some organization like VisualBasic.org to take it on as an open source/community endeavor. If Microsoft doesn't want it and lots of other people do, why not?
">> Full Visual Studio is now free !
Well they had to do something to keep folks from talking about VB6 for a few days."
Certainly there seems to be a lot more interest in VB6 than .Net. But I suspect there is more to Microsoft's move than simply diverting attention from VB6 programming.
With Microsoft it is always difficult to understand their intentions, and their plans change frequently anyway.
Is it a move to strengthen .Net or to move away from it ?
Who knows? Probably few even within Microsoft.
Either way, it is good that VB6 programming and VBA programming continue whatever happens to .Net.
>> Full Visual Studio is now free !
Well they had to do something to keep folks from talking about VB6 for a few days.
Full Visual Studio is now free !
Visual Studio 2013 is now free for individual developers and for teams of up to 5 developers.
It's the community edition which is the same as the professional edition.
Good to see Visual Studio has now found it's true market value.
Yes VB6 still installs and runs VB6 compiled applications on Windows 10. Cannot guess in future Windows versions but hope it will run.
It would be good on Microsoft's part if they open source VB6 for the vast community who can take it over further. But it will never do so as Visual Basic for Applications (VBA) is built into their MSOffice products.
VB6 is the only COM language other than C/C++. Dot net does not properly support the webbrowser control. Also, it was Microsoft's open attitude toward the developer community that caused it to become dominant in the first place. I believe MS would do very well to bring back a VB-COM IDE, and/or modernize it.