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)
      • 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.

      • Richard Gump commented  ·   ·  Flag as inappropriate

        MS has proven it only cares about its Stock Holders and not the people who have put them where they are. I know they would be surprised at how many copies of VB6 they would sell if they came back out with it. You can tell this by the way they drop support for products and make it very difficult for some products to work properly as Windows moves forward with versions.

        I could go on and on, but MS doesn't care, and for those of you who do, I would just be preaching to the choir.

      • Wizard of Oz commented  ·   ·  Flag as inappropriate

        @Damien HOFFSCHIR

        Man, you are a fool.
        No one is stuck in VB6, is simply better than C. VB6 programmers know at least 3-5 different languages. I doubt that those in C # know more languages than VB6 programmers (and I doubt C guys know more assembler than VB6 guys), so, who is stuck ?!

        Regarding Tiobe, you are delirious. Tiobe is for programming languages as Nature journal is for science.

      • Andy Gable commented  ·   ·  Flag as inappropriate

        I use VB6 daily with my Company

        I have customer running up to 30 checkout Lanes (EPoS Software Written in VB6 as well as the Back office Software)

        SO a Newer version of Classic VB6 would be fantastic. I have tried to move the systems into .net BUT everytime I try I get over 3,000 Compiler issues With in VB6 I can add new features and have them working with in a few hours

      • SuperDre commented  ·   ·  Flag as inappropriate

        Don't want to burst your buble, but TIOBE index doesn't say anything, it just says that (visual)basic was used a lot in search engines, but that doesn't mean it's talking about VB6, it's Basic in general...
        Yes I'm still using VB6 for work and I do hope they release a real updated version (would love to actually see the real VB7 which was said to be feature ready (which doesn't ofcourse mean actually ready) but never released) and 64bit compilation..

      • Anonymous commented  ·   ·  Flag as inappropriate

        VB6 over taking .Net on the TIOBE index of most popular languages is not an aberration that can be easily dismissed. The VB6 community, still in 2014, is significant. Very!

        Microsoft please honor this huge community with a 64bit version of VB6. Thank you!

      • THEO commented  ·   ·  Flag as inappropriate

        What MS should really be focused on is having developers who can solve client problems with their code hooking more people exponentially on their platform. Them waging an idealic war of programming language purism is foolish. Watching them try to squeeze more performance out of .net through complex gyrations and contortions is insane. You had a solution, it was native code. And you had a higher level language that produced it along with pcode capabilities. .net is like the out growth of academic mental masterb**ion. It can't be about money, given that surface lost 1.2billion last year. Throw us a bone here, it will only bolster you platform with user and dev lock in, not to mention releasing some of the bad blood this fiasco has created. Independent developers and business solution providers are small shops. We can not shoulder having millions of lines of code obsoleted arbitrarily. This isn't going away, we aren't going away. This is a real problem. HEAR OUR VOICE

      • ali commented  ·   ·  Flag as inappropriate

        Bring back Classic Visual Basic (VB6), and allow 64 bit compilation


      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      Feedback and Knowledge Base