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
ANIMATION of the Visual Basic 6.0 incandescent bulb (simple GIF images): http://vb6awards.blogspot.com/2014/11/visual-basic-60-incandescent-bulb_8.html
Full Visual Studio Now Free
Full Power, No Charge: Visual Studio Community 2013
Coinciding with the announcement that Microsoft is open sourcing .NET, the firm has released a new edition of Visual Studio Professional 2013. Dubbed Visual Studio Community 2013 (VSC2013), this release is available now and free to use for the many popular usage scenarios.
In this case free means that VSC2013 is available for use without additional cost to individual users, non-profit users, and non-enterprise organizations. Microsoft was able to produce VSC2013 so quickly because it fundamentally is a rebranded copy of VS2013 Professional. This means users will find a tool more capable than the previously released Visual Studio Express editions. Developers can use Microsoft’s flagship offering to target the obvious Windows platforms as well as Android, iOS, and Unity.
As noted by the Microsoft OneCode Team, VSC2013 supports the plugins in the Visual Studio Gallery, making this edition more useful than Visual Studio Express which cannot use extensions. For those in corporate settings, Visual Studio Professional remains available.
VSC2013 is available via the usual web installer and full DVD ISO options. It comes with Update 4 applied.
Sten2005 - vote for VB6 programming commented
The guide to installing the VB6 IDE on Windows 7 now has 397,000 views:-
And there are guides for installing VB6 programming on Windows 8 and Windows 10 too.
TRUE: VB6 is pure genius. Code, compile and ship.
One of the thing that I hate so much about .NET is the runtime library. Too many version:
.net framework 2.xx
.net framework 3.xx
.net framework 4.xx
urggh.. and sometimes you need to install .net 3.xx and 4.xx side by side to make your applications works correctly :(
VB6 is pure genius. Code, compile and ship.
Microsoft Launches Free, Unrestricted Version Of Visual Studio For Small Teams
“The simple way to think about this is that we are broadening up access to Visual Studio,” Microsoft’s corporate VP of its Developer Division S. “Soma” Somasegar told me in an interview late last month. Somasegar told me that the Community Edition will allow you to build any kind of application for the Web, mobile devices, desktop and the cloud. “It’s a full features version of Visual Studio,” he noted. “It includes the full richness of the Visual Studio extensions and ecosystem.”
This means you get access to all the usual Visual Studio tools like Peek, Code Analysis, Graphical Debugging and more.
The shift that’s happening here is Visual Studio is basically going freemium. Microsoft has now built a set of online tools around Visual Studio Online (which is also getting a number of updates today) that it believes people will pay for. The Visual Studio IDE is now the gateway into the rest of that ecosystem and the more developers Microsoft can get onto that platform, the more will also want to use the rest of the company’s (paid) toolset through subscriptions to MSDN and other channels.
Please, don't say how good the visual studio is !!!! IT IS NOT GOOD ! VB6 is 1000000 times smarter ! So,make a vb6 that opens and runs all the old vb6source code projects!
Great news new and FREE Visual Studio Community is ready to download. Stop wasting your time to reincarnate VB6. Develop great cross platform apps freely with a great and FREE IDE. Thanks Microsoft
"Visual Studio Community 2013 is a new, full-featured, and FREE addition to the Visual Studio product lineup. View demos that highlight multi-device apps across Windows, Android, and iOS, and that show how Visual Studio Community can be extended to support additional languages like Python."
VB6 Programming commented
It isn't very responsible of you to advise developers who don't already use .Net to learn it now - just as Microsoft are sending .Net to the open source dumping ground.
Yes, legacy .Net apps will continue for years to come - but Microsoft will have little future involvement.
At least Microsoft haven't abandoned you overnight as they tried to do with VB6 programming.
why so much effort in creating an alternate to VB6. All those efforts can be spent to learn .NET which is already a wonderful platform. I would say don't waste your time and learn .NET, which I did and I am a happy camper. You will be amazed to discover the wide and wonderful world of NET.
What a joke ! listen to this one: "Microsoft: Nobody loves developers more than us" ! then why not draw a new version of Visual Basic 6.x ?! oh, yes, Microsoft loves developers ... I almost forgot ...
Bring it back