Though it wasn't stamped with a red DECLINED, Microsoft also wasn't budged by a famous petition (no longer available on the defunct circulating about 10 years ago, signed by Microsoft MVPs, "for the development of unmanaged Visual Basic and Visual Basic for Applications." Not that VB6 enthusiasts are totally out of luck.Last August, we covered a "Free Tool Offered as Classic Visual Basic Successor" from B4J.
NET using more computer resources and being a Java clone.
Thumbs up for this." For its part, Microsoft has extended support for the VB runtime through 2024 and provided migration and upgrade guidance.
"It is not feasible to open source VB6 tools chain and ecosystem," Yuknewicz said. (btw: Here's an example post on Slashdot from the "those who love to hate it" camp: "Let it die.
It's a terrible language and it should die a death.
don't open source it or you'll just encourage a new wave of cheapskate programmers to start learning bad habits and producing crappy code.") Platt's new take on the issue is to "develop a version of VB6 that produces HTML5." Sure enough, Platt's column found its way into a User Voice item as support for the VB6 cause.
Even though Microsoft didn't, you might as well go ahead and stamp Platt's idea DECLINED.
For the most part, anything that worked on Windows 7 works on Windows 10. Well, like many companies out there, mine has a few proprietary programs that were written, long ago, in VB6.
Visual Basic 6 (VB6) has been one of the few exceptions, so far. The apps work great, so it just hasn’t made sense to spend the time and/or money it would take to upgrade them to VB. Yet, we still need to be able to make minor changes to the programs now and then.
VB6 supporters couldn't help opening up old wounds in the comments section of that article, with one reader saying: "When I knew all the answers, Microsoft changed all the questions.