I suggest you ...

12,081 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    EugeneEugene shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    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.

    Paul Yuknewicz
    Group Program Manager
    Microsoft Visual Studio Cloud Tools

    7696 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • JoJo commented  ·   ·  Flag as inappropriate

        Microsoft Doesn't Budge on 'Classic' Visual Basic

        Despite renewed developer hue and cry to do something with "classic" Visual Basic sparked by the recent 25th birthday celebration for the programming language, Microsoft is showing no signs of caving in and revitalizing the language, moving it to open source or anything else.

        https://adtmag.com/articles/2016/05/24/microsoft-visual-basic.aspx

        "Clearly this issue won't go away, closing this suggestion doesn't close down the demand for VB6 programming."

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        There is a new 4.8 release of the VS6/VB6 installer wizard available at http://nuke.vbcorner.net/

        The wizard simplifies the installation of the VB6 programming IDE on Windows 10

        With over 105,000 downloads, the installer is well proven.

      • kontexkontex commented  ·   ·  Flag as inappropriate

        What is the performance for that? Just a text or something.
        A global community should raise this amount.

      • axisdjaxisdj commented  ·   ·  Flag as inappropriate

        In case anyone is wondering, I asked Alan Cooper for a consultation on moving forward with a vb6 replacement to get some advise.. his rate is $1500 an hour. I think his insight may be worth it, just wanted to let everyone know.

      • Microsoft, update VB6 programming & VBA programmingMicrosoft, update VB6 programming & VBA programming commented  ·   ·  Flag as inappropriate

        Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1, Windows Server 2012, Windows 10, and Windows Server 2016 -
        5/16/2017

        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 Vista
        - Windows Server 2008 including R2
        - Windows 7
        - Windows 8 and Windows 8.1
        - Windows Server 2012 including R2
        - Windows 10
        - Windows Server 2016

        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.

        The VB6 runtime will ship and will be supported in Windows Server 2016 for the lifetime of the OS.

        https://docs.microsoft.com/en-us/dotnet/visual-basic/reference/vb6-support

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        >> Alan Cooper is correct, you can do the same thing in any language. Any claim otherwise is just a "my religion is better than your religion" argument.

        Bingo!

      • PaulPaul commented  ·   ·  Flag as inappropriate

        @axisdj

        "Alan thinks the programming language has been the same for the past 40 years. They do the same thing and there is no difference between them"

        In many ways the 80's and 90's were they heyday of language development. C++, MATLAB, Objective-C, Perl, Python, Visual Basic, Ruby, Java, Delphi, JavaScript, PHP and many others were developed then.

        Many of these 'last millennium' languages are still the leaders today.

        With the slight exception of functional programming (which has had more academic success than commercial) there has been little advance this millennium. .Net was developed around the turn of the millennium as a clone of Java. Apple's Swift (effectively an update of the 80's Objective-C) is growing as is Google's Go, but otherwise this millennium's languages haven't taken the programming world by storm.

        Alan Cooper is correct, you can do the same thing in any language. Any claim otherwise is just a "my religion is better than your religion" argument.

      • axisdjaxisdj commented  ·   ·  Flag as inappropriate

        Quote From Alan Cooper:

        Alan thinks the programming language has been the same for the past 40 years. They do the same thing and there is no difference between them. He says,

        “You can look at all these different languages and point to all the differences but the differences don’t mean much.”

        A few years ago, Alan started working on something interesting but his code was repeatedly crashing. He started pulling out his code and testing it but couldn’t find the problem. Finally, he started testing .NET and realised that was where the issue lay. It was using the same code for the past 20 years. They hadn’t rewritten the kernels. His program was crashing because he was asking .NET to do what the rulebook said it couldn’t do. Programming languages don’t let you express outside of what they expect you to want. He says,"

      • Anonymous commented  ·   ·  Flag as inappropriate

        A new release of the NS Basic programming language is available.

        http://blog.nsbasic.com/

        NS Basic is a language and IDE for developing web and mobile apps and is similar to the VB6 programming language.

      • axisdjaxisdj commented  ·   ·  Flag as inappropriate

        LofaDay, please know I had no choice, I still think vb6 is better in so many ways, but I need true cross platform support.

      • Lofaday - www VB64 com - A new IDE is on its wayLofaday - www VB64 com - A new IDE is on its way commented  ·   ·  Flag as inappropriate

        @Microsoft, update VB6... What I find interesting about the semi-failure of MS's Win 10 Store is that, as usual, MS seems to have misunderstood it's own success elsewhere. The entire web was and is it's store. Google an app, see an app, download the app, install it, done. EVERYONE DOES IT. We don't need no managed store to complicate that!

        I'm not hugely familiar with Android (I have a Galaxy Note) but it seems that I HAVE to go thru their store. WHY? So in a word, I won't be rushing to put an app on a store.. it it's good enough, people will find it. VB6 or whatever.

        At Axisdj, er sorry mate, glad you found your solution, but VB6 it ain't :-)

      • jeremygjeremyg commented  ·   ·  Flag as inappropriate

        At my age of 25, I believe that Visual Basic 6.0 is, by far, the most powerful language ever made !

      • jeremygjeremyg commented  ·   ·  Flag as inappropriate

        At my age of 25, I believe that VB6 is, by far, the most powerful language ever made !

      Feedback and Knowledge Base