I suggest you ...

12,081 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Eugene 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


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      • VB6 Fire commented  ·   ·  Flag as inappropriate


        You're right, some says it was a sabotage from within Microsoft to hamper a new VB6 development, others say that Microsoft does not have the expertise to make a new VB6.

        My personal opinion is that Microsoft will make a new version of vb6, we are simply too many programmers. I'm glad we started to come together as a community and speak our minds.

      • Anonymous commented  ·   ·  Flag as inappropriate

        The longer they wait to respond the better GCC (and the like) look to me. That is, platforms that can create highly efficient applications that are immune to Microsoft's dev tool death clock.

        Most every language out there that has made a difference in the industry have modern development efforts: ADA, COBOL, Algol...C. Not VB6. Not without re-coding large applications (.Sweat).

      • SuperDre commented  ·   ·  Flag as inappropriate

        7000 votes might not be much, but for a site which most people/developers never heard of, it's still a lot. I only knew about this site because of a comment in the vbforums site and I'm an active developer and some other collegues of mine also never heard of uservoice..

      • piper commented  ·   ·  Flag as inappropriate

        For me and my environment it's more and more a question of a future WITH or WITHOUT Windows. An evaluation task for the second case is started, but nobody is happy about that.

        Please, MS - SOS - Save Our Souls!!

      • piper commented  ·   ·  Flag as inappropriate

        Bring it back! I would pay - say - 500$ for an updated/actualized version!

      • Anonymous commented  ·   ·  Flag as inappropriate

        It would be really interesting if MS would actually update VB Classic but lets be a little pragmatic about this. If there were 3 Million developers using MS products you would need 30K signatures to equal 1%. 7K isn't necessarily a small number but it's less than 1%.

        If there were 1 Billion MS desktops in the world you would need VB Classic apps running on 10 Million of them to equal 1% of the market share. Not impossible but how do you compile the data?

        I wrote hundreds of thousands of lines of VB6 code over the years so I certainly feel everyone's pain about this. The reality is Technology, Microsoft and the World for that matter have moved on. Modern applications have to accomplish so much these days and be so flexible... I can't imagine using the old VB language for this purpose.

        How do you deal with a World that has moved to the Web and now Cloud based solutions all running on phones and tablets with a language like Classic VB? For all of the client/server line of business apps out there you might be able to pull something off but without the extensibility of the newer languages you're going to eventually run out of technology.

        I get the argument being put forth here. It makes sense on many levels but you might want to consider moving on. If for no other reason than to cover yourself as a professional developer. It only hurts for a little while.

        Good luck to everyone with this. I did cast a vote to do this purely because there are too many businesses out there who simply cannot or choose not to pay re-development costs. Microsoft should choose to assume some responsibility here. Porting to a 64 bit compiler is work but it's nothing they can't handle.

      • Anonymous commented  ·   ·  Flag as inappropriate

        simply we need visual basic 6 mean VB6 with advance features,
        because VB6 is a great language 100%.

      • dee-u commented  ·   ·  Flag as inappropriate

        I don't think 7000 votes is a lot of votes, if we get probably a million votes then MS will here us.

      • VB Coder commented  ·   ·  Flag as inappropriate

        Microsoft - this vote has reached 7,000.
        It is now time for you to reply to the call "Bring back Classic Visual Basic, an improved version of VB6".
        It is over 12 years since you tried to kill the VB6 programming language. It isn't going to go away.

        Now we need an answer from you. Will you update VB6 to have 64bit support as you did for VBA ?

      • VB6 Programming commented  ·   ·  Flag as inappropriate

        7000 votes for the return of the VB6 programming language.
        And still Microsoft won't even do us the courtesy of replying to this thread.

      • Mike Challis commented  ·   ·  Flag as inappropriate

        My current client has a huge investment in VB6 code, and the codebase is being developed further by a team of developers. To migrate the code brings little benefit and the cost is significant.

        Bring back an updated VB6 (64 bit) that compiles current VB6 code.

      • Anonymous commented  ·   ·  Flag as inappropriate

        My clients would not consider a full rewrite (and corresponding huge $$$ hit) of moving their VB6 app to .Net or Java. Most would be open to a minor upgrade to a 64-bit version fee scale. This means that if Microsoft gave us a 64-bit version I'd make chunky $$$.

        I suspect there are many others in the same situation.

      • axisdj commented  ·   ·  Flag as inappropriate

        Winston potgieter commented · Delete…

        oh just an antidote.. facebook one of the most valuable internet companies in the world stuck to a strict and PURE OOP and design pattern regimen, or else it would not have worked.. NOT!!!!

        We don't need pure OOP to write good software. Bring back vb6, you can add what you want, but let it compile what we have today.

      Feedback and Knowledge Base