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 Classic Visual Basic (VB6), and allow 64 bit compilation
Lok here: http://vbvs.cloudapp.net/
If it ever became a mandate from the customers to change to another programming language does Microsoft really think we'd choose a product by them if they left us high and dry [rhetorical].
Can you imagine if the current owner of Java (Oracle) saying "NO MORE JAVA". You have to switch all your code to PL/SQL. We know it powers x million devices but we are going to dictate what you need to use. Look we'll even throw in a Java to PL/SQL conversion tool that will work with small programs.
New Motley Fool article. Motley Fool believes MS is changing for the better. This can effect VB6. Read\create comments (VB6 entries).
VB6 Fire commented
A comment from Manuel Barradas posted to the Visual Basic 6.0 page: "it may just be a coincidence, but windows sales are slowing down since MS introduced .NET development. I was a VB6 Programmer and everything was done easy. Lots of people like me who had to make a move to learn VB.NET they simply learned another FREE language like java not the ****** IMENSELY HUGE LIKE all the FRAMEWORK VERSIONS. The frameworks are 70% of windows 7 disk space. THIS IS TERRIBLE java is only 200mb !!!!!!!
Besides java I still Use VB6 the best language ever made.!!!!!!
An advise to MS KISS Keep It Simple Stupids. VB6 is KISS,
if you make a new VB6 for 64bit tech your marketshare will skyrocket. Put your surface tablets to run new VB6 and they will fly off the shelves because the there will be a BOOM in new APPS."
Purchased last year Visual Studio .net 2002 Enterprise for US$20.00
"8. DOWNGRADES. Instead of installing and using the Product, you may install and use one copy of an earlier version of the Product, provided that you completely remove such earlier version and install the original Product within a reasonable time. Your use of such earlier version shall be governed by this EULA, and your rights to use such earlier version shall terminate when you install the original Product."
There is the free VB5 Control Creation Edition. ocx and dll only but you can host in IE
@Googleman: Even if you couldn't buy it anywhere anymore, it would still be illegal to just provide it as a download without the approval of Microsoft..
Because you can't buy it anymore doesn't make it free...
Also when did MS start making breaking changes ? This is unacceptable:
Microsoft do still supply the VB6 programming language -
Visual Basic 6.0 Enterprise Edition is distributed by Microsoft as part of a MSDN subscription:
VB6 programming language on Ebay.
VB6 Professional $499
It is illegal to download VB6.
You can buy it on Ebay.
You can get it as part of a Microsoft MSDN subscription.
Google Man commented
you can not buy VS6 from anywhere, so it's free ! People want to buy VB6 but from where ?!
@Licoare: please remove the link as it links to an illegal version of Visual Studio 6.. And that's not the way to go about it..
Visual Studio 6.0 (Visual Basic 6.0) download from here:
MS must be blind and does not really know the scope of the support VB6 still has. There so many good Apps out there written in VB6 e.g. Malwarebytes Antimalware, MyPhoneExplorer etc.
They should run some statistics on searches for VB6 code and will be more than surprised maybe even shocked.
Also our flagship "DDownloads" (an App Store with Modern UI) is written in VB6
Microsoft pelase bring us back Classic Visual Basic, and allow us 64 bits compilation.
I believe that MS is just losing a large source of income by not updating VB6.
Not to say that the current version has really hindered me in developing new, complex, line-of-business applications. As they are mostly based on databases, my clients and myself are very happy with the database response times...far better than .Net.
Is it just snobbish pride, or saving-of-face, for MS not to admit that VB6 is the most popular MS language currently. There is no shortage of work available here in Australia/New Zealand for good VB6 programmers – maintenance and new projects.
I don't know, just keep it for now, but I just don't think it will be fronted.. but who knows..