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…)
    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

    8360 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...
      • axisdj commented  ·   ·  Flag as inappropriate

        from a blog post.

        I've already converted my 350,000 lines from VB6 to VB.NET, but am not releasing the 'new' version, because no matter how much I change the algorithms in the program and use the features of the new environment, the performance is miserable.

        VB.NET is a very poor performer, and converting to it is not an upgrade from the end users' perspective. The IDE is slightly richer, yes, but it's dog slow - even though I'm running it on a computer with far more than ten times the power I used for VB6.

        "Visual Fred" is an extreme failure from my perspective. Utterly incompatible, massive pointless effort absorber, extreme costs for no results. Towering example of "change for change's sake."

        Microsoft's grade on Visual Basic evolution: F-

      • SuperDre commented  ·   ·  Flag as inappropriate

        Basic4Android is nice, but you won't get me to do VB4J EVER!!! there is a reason I shun away from Java... B4A is another matter as it compiles to native code for android, but if they ever get it to compile to native code for windows/linux it might be interesting..
        If you want to get into Android and you are a VB6 developer, B4A is definitly a tool to take a look at..

      • Visual commented  ·   ·  Flag as inappropriate

        For those who vote 1 vote, you must know that your 1 Vote is actually in support of VB6 ;)

        Bring back Visual Basic 6.0 !

      • Visual commented  ·   ·  Flag as inappropriate

        For those who vote 1 vote, you must know that your 1 Vote is actually in support of VB6 ;)

        Bring back VB6 !

      • Anonymous commented  ·   ·  Flag as inappropriate

        For over thirty consecutive years, I have been developing systems and producing software
        applications for local and international companies using mony different languages; I found that
        the applications which were developed in VB6 since 1998 are still working with a good condition upto the moment, but others disappeared.

      • Spaceman commented  ·   ·  Flag as inappropriate

        public sub Form_Load()
        MSGBOX("and Microsoft please make it with support """PERSIAN""" language")
        end sub

      • Spaceman commented  ·   ·  Flag as inappropriate

        I think VB6 most back with the most powerful than all computer programming languages
        we love VB6
        if VB6 back to best why we should go to .NET???
        .NET have very more line code than VB6 and VB6 is easier and the best
        all Programmer most write a program with more less line code for making a good software
        Microsoft don't worry about upgrade VB6
        please do it fast
        we will wait to VB6 back
        With Respect

      • Kayl commented  ·   ·  Flag as inappropriate

        We need just 69 votes to go from place #7 on place #5 on the idea scale on MS site !

      • VB6 Programming commented  ·   ·  Flag as inappropriate

        Yes, I'd hope that an updated VB6 would just be a slight refresh. Any more and, with Microsoft's recent history of incompetent decisions, it wouldn't be compatible with anything !

      • Anonymous commented  ·   ·  Flag as inappropriate

        Yes if nothing else just keep OS compatibility with vb6.

        i doubt they could make a vb7 that had good value anyway from looking at their design decisions lately. Soebski link is a very good read thanks

      • Sergey commented  ·   ·  Flag as inappropriate

        Why do we need VB7, if VB6 works well? Continue to work on VB6.
        Axe and Hammer were not changed in the last few thousand years.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Vb6 strikes that rare balance between highly functional, and elegantly simple. I would have switched if there was a real competitor for what it offers but there isn't. I can't believe they won't continue it, it has to much to offer. I still write new code everyday in it. A programming language should be allowed to live and grow. If C had been obsoleted in 4 years where would all of computing be today. Developers need language continuity, as do businesses

      Feedback and Knowledge Base