I suggest you ...

12,081 votes
Vote
Sign in
Check!
(thinking…)
Reset
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

    8520 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • MichaelE commented  ·   ·  Flag as inappropriate

        As a young developer you should be investing in Java, C, C++ and Python first. C#, Javascript and Ruby certainly cant hurt. According to this and other sources: https://www.tiobe.com/tiobe-index/

        A wise young developer though ultimately should deep dive into what is native to Android and iPhone mobile\tablet platforms.

        If this is a troll post I expect a "you should only ever use .Net" kinda noise. In the adult professional programmers world one should always be open to new languages and trends.

        In so doing you might find a great appreciation for VB6 as getting a lot right...and in some ways still unmatched in simplicity and power. How 'bout that!

      • Martha commented  ·   ·  Flag as inappropriate

        As a young developer I would say VB6 is dead and in Zombie state. The last Stack Overflow Survey 2018 was the final straw for me. I would encourage everyone to opt for .NET instead, which is modern, uptodate,slick and has a great future.

        Stack Overflow Developer Survey 2018 https://insights.stackoverflow.com/survey/2018/

      • Davor commented  ·   ·  Flag as inappropriate

        I want to say that vb6 and VBA are not dead.
        There is still a lot of new development.
        For example, I created a new tool to connect vb6 & VBA to Microsoft Azure cloud that gives developers the possibility to monitor (log or track) usage & performance of their apps in real-time online. The project is here: https://VBATelemetry.com

      • jovanyt commented  ·   ·  Flag as inappropriate

        @RabidVB6ster

        You are back Zagor theShit ?Welcome back our ho&re :)

        .NET does not exist on the map, all of .NET languages are artificially maintained.

        Most dreaded ? I bet that you have something to do with that. Just one troll amateur programmer is needed for such a path^etic poll.

      • RabidVB6ster commented  ·   ·  Flag as inappropriate

        As a rabid VB6 community member, I think we need to re-think our strategy. May be the best option is to go ahead and learn .NET, which is the best out there (of course VB6 will still be the best in our obstinate minds and incessant rantings).

        The reason is that once again, for the third consequent year VB6 has been elected as the MOST DREADED Language by the millions of programmers.

        Check it out for yourself ==>

        Stack Overflow Developer Survey 2018 https://insights.stackoverflow.com/survey/2018/

      • jovanyt commented  ·   ·  Flag as inappropriate

        @LOL

        D E V E L O P E R S U R V E Y R E S U L T S 2018 is done with moro*ns that don't know shi-t !

      • kontex commented  ·   ·  Flag as inappropriate

        only what is good you have to fear. VB6 is bad for wage slaves who think "the main thing I have work". For me it is so that I reach my goals quickly with VB6 and have money and free time

      • LOL commented  ·   ·  Flag as inappropriate

        D E V E L O P E R S U R V E Y R E S U L T S 2018

        VISUAL BASIC 6 IS CROWNED AGAIN AS THE MOST HATED LANGUAGE BY WORLD PROGRAMMERS!

        Also for the third year in a row, Visual Basic 6 ranks as the most dreaded programming language. Most dreaded means that a high percentage of developers who are currently using the technology express no interest in continuing to do so.

        Visual Basic 6

        89.9%

        Cobol

        84.1%

        CoffeeScript

        82.7%

      • kontex commented  ·   ·  Flag as inappropriate

        >> So Rust and Kotlin are the most popular languages !!!

        laugh very loud.

        >> Get real.

        How can you expect to determine the opinion of other people if:
        - enjoy working with VB6
        - you reach your goals quickly and easily with VB6.
        - nobody cares the user for which programming language one uses.

        God or troll ?
        (or coward because anonymous)

      • MichaelE commented  ·   ·  Flag as inappropriate

        I concur with kontex. Everyone should only use the best computer language every made. Assembler. We really dont need to finish rock-solid applications in a fraction of the time done in VB6. Our families are used to not seeing us because its more important to code using the right language than be with them. Plus VB6 will only work as long as there is a Windows OS. What good is that!

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

        @retired coder, yep. I started an IDE in VBA but doubt folk will download it, let alone adopt a VBA app. I've used and been impressed with online IDEs such as mbed c++ (google "mbed IDE" images). Alum removes the "VB" stigma while retaining the paradigm. It should also appeal to those who like the look and feel of C & JS. Despite being on-line, it still has fast responses, option explicit, as much VB compatibility as possible (even VB64 couldn't achieve 100% compat'). I plan it to be as open and free as possible, but needs some way of funding. By the way, the IDE isn't all mine -- it uses Codiad and Ace, both well established open-source. The VBA paradigm is managed with a server-side fast transpiler (pseudo compiler). Thanks for asking :-)

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

        @Anonymous, yes, it's horses for courses. Dot NET has it's place if speed and stability is not essential (same as Python, JS etc).

        I think the biggest difference is .NET was a paradigm shift in the way developers think. You mention a vast eco system of libraries ... it's almost as if Google is an intrinsic part of the IDE these days. Imagine there was a time where if you needed a specialist app, instead of googling for it, you just did it yourself in a day or 2. Then you got your own truly extensible and ultimately supportable library.

        3 examples I did • a fast specialist "uncrashable" multi-node mirrored database for a critical uptime information system that was relied on daily by millions of passengers;• a complex visual mechanism simulator that calculated all the angles and ran simulations at 25fps;• an IIS that could take a single cross referenced book or manual in MS Word and generate a full website from it. All that was a breeze. I've tried to do that kind of thing with the modern "google that library" approach and the answer is it takes longer, it's far more frustrating, and if it doesn't work (eg: due to update), you can't fix it -- try explaining that to an MP/senator. But of course VB6 (and Alum - I hope to be it's successor) has it's limitations. It is simply a DIFFERENT TOOL for which there is no parallel.

        To me, VB6 to C# is like Excel to Sage for an accountant. Everyone knows how to use Excel, but if you want something with accountancy approved modules etc, if you are using it full time, go to Sage. So far, so good. Now imagine if Microsoft said to the world, you know that thing called Excel you all use and love, well, we're pulling it. And you might as well take it off your CV too because all that expertise is gone -- we own the patents, and we are not going to let anyone else sell it. Furthermore, just for good measure, we are going to start a campaign to make it look like it was amateurish. Then our preferred Sage users can sneer at you too. Imagine what the Excel community (who still use VBA by the way) would say to that?

      Feedback and Knowledge Base