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

    7635 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...
      • jeremygjeremyg commented  ·   ·  Flag as inappropriate

        F olks, d on't re spond t o the bo t "Z agor Ten ay". It's an aut omated b,ot. Please look at the conversation. It chooses simplicity and is answering with a question. The rest is a generated counter attack text based on our previous comments ! It simply inserts words in a composed text based on our comments.

      • jeremygjeremyg commented  ·   ·  Flag as inappropriate

        F olks, d on't re spond t o the bo t "Z agor Ten ay". It's an aut omated b,ot.

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate

        @jeremyg
        You did not answer my question.

        What do you think about Stackoverflow results saying VB6 is the most hated language? What is your opinion?

      • jeremygjeremyg commented  ·   ·  Flag as inappropriate

        PS: What your mind can't comprehend is that the VB6 app's that I have showed you need the highest levels of science and engineering. Is this simple for you ? If it is show me a MojoJojo app and a .NET app that are close to those VB6 open source apps. :D

        VISUAL BASIC 6.0 is KING !

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate

        "Yes I did try and mogiojojo has an error from the start"

        I did try too and it worked. Xojo does Mandelbrot faster than VB6. What do you think?

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate

        @jeremyg

        What do you think about Stackoverflow results saying VB6 is the most hated language? What is your opinion?

      • jeremygjeremyg commented  ·   ·  Flag as inappropriate

        @Zagor Tenay

        "These apps at vb6awards are very simple. You can do more with .NET."

        PLEASE SHOW ME A .NET APP THAT IS MORE ADVANCED THAN WHAT I SHOWED YOU IN VISUAL BASIC 6.0 !

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate

        @jeremygjeremyg

        What do you think of BX4? They say it is much better than VB6. You can do cross-platform with it.

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate

        @jeremyg

        I have downloaded and tested Xojo and VB6 from this website. Xojo is really much faster. Did you test it on your computer? Does it mean that we should drop VB6?

      • jeremygjeremyg commented  ·   ·  Flag as inappropriate

        @Zagor Tenay

        Just show me an app made with that wannabe tool (MOgioGiogio). Give me the best example you have. Impress me.

      • jeremygjeremyg commented  ·   ·  Flag as inappropriate

        @Zagor Tenay

        "Also can you please tell me why MojoGiogio is slower than VB6?"

        Yes I can tell you why VB6 is faster. VB6 is faster than C++ ! Your wannabe tool is nonexistent in any speed contest. Stop the false posts on your own forum.

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate

        @Microsoft, update VB6 programming

        Can you please explain what you think about the Stackoverflow 2017 survey which states that VB6 is the most hated language? Why should anyone use VB6 and even run it on ARM computers?

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate

        @MichaelE

        I am a real person, don't worry. My question is simple and you can answer with one line if you want. I repeat. Would you kindly tell me if you worked with .NET?
        Thank you in advance.

      Feedback and Knowledge Base