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

    8408 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...
      • Spaceman commented  ·   ·  Flag as inappropriate

        *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
        *-*-*-*-*-*-JUST VB6*-*-*-*-*-*-*
        *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

      • Sanio Montenegro commented  ·   ·  Flag as inappropriate

        ¤*¨¨*¤.¸¸…¸.¤\
        \¸ ♥ VB6 ♥.,.\
        .\¸.¤*¨¨*¤.¸¸.¸.¤*
        ..\
        ☻/
        /▌
        / \
        _______________________

        Bring back Visual Basic 6.0 !

      • axisdj commented  ·   ·  Flag as inappropriate

        @FB Cufar , the reson I posted this, is that it makes a point that non-managed development is making a comeback, and has benefits in todays technology environment. In the last part of the video it shows where dev money was spent and vb6 is included. The whole point is that there is still a need today for a vb6 style dev environment that compiles natively, remember all code written in vb6 compiles via the vc++ compiler.. it interprets the basic syntax and converts it to c++ then compiles. So in essence vb6 produces the same code as vc++.

        Bring back vb6, native is cool again for so many reasons, and with an simple syntax like vb6 can be so powerful!

      • Mulan X commented  ·   ·  Flag as inappropriate

        I agree with everything said.
        i even use some old school exe vb6 files to do some dirty work i dont want to rewrite in .net...

      • George Hutson commented  ·   ·  Flag as inappropriate

        ╔═.♥. ═════════════════════════╗

        ................ Bring back Visual Basic 6.0 !

        ╚══════.♥. ════════════════════╝

      • J River commented  ·   ·  Flag as inappropriate

        ¸¸.•*¨*•*´¨)
        ¸.•´¸.•*´¨) ¸.•*¨)
        (¸.•´ (¸.•` ¤ I love Visual Basic 6.0 !

      • axisdj commented  ·   ·  Flag as inappropriate

        a comment from code project:

        I'm the author of the PhotoDemon project mentioned above (which should point to photodemon.org instead of an old Planet Source Code article). I thought I'd share my $0.02 on VB6.

        VB6 is not a perfect language. No language is. But it does offer some unique benefits that many of its competitors lack, despite being nearly 15 years old.

        One of VB6's greatest strengths is its portability. Privacy is an enormous concern for many people, so interest in portable applications - e.g. apps that can be run from a thumb drive without installation or admin rights - is higher than ever. VB6's lack of external dependencies makes it an excellent choice for portability, and is the primary reason I chose VB6 for PhotoDemon. VB6's runtimes are included by default on all versions of Windows (XP through 8.1) meaning anyone can download a VB6 application and run it without installation or admin rights. That's huge. .NET's versioning **** and enormous size make it a poor choice for portability, and there are simply no other languages that provide the combination of portability, RAD, and performance that VB6 does.

        Let me elaborate on performance a bit, since PhotoDemon is a project where performance is a primary concern. VB6 remains an excellent choice for coders who care about performance. As a language with support for native compilation, it tends to outperform purely interpreted languages (java, js, etc), while staying competitive with similar code from a modern C/C++ compiler. As an example, PhotoDemon outperforms both GIMP and Paint.NET in a number of areas, and while that's more demonstrative of good algorithms than good compilers, it goes to show that performance is still a perfectly valid reason to stick with VB6.

        Surprisingly, VB6 is also a reasonably good solution for cross-platform development where performance is crucial. (Obviously HTML/javascript is much better for less performance-intensive operations, but for things like photo editing, they remain insufficient.) VB6's simplicity means its code actually runs very well under Wine, and it does not suffer the same woes as .NET projects reliant on Mono. There are no perfect solutions for cross-platform development, but VB6 is a surprisingly good choice for performance-intensive, UI-centric cross-platform applications.

        I could go on for some time, but ultimately the arguments for/against VB6 should boil down to this: can it still be used to write quality applications? I think projects like PhotoDemon demonstrate that it can. For all its faults, VB6 continues to fill a niche that its successor (VB.NET) and "competitors" (Xojo, PowerBasic, etc) do not, while still remaining true to the BASIC heritage. As a developer who works in everything from PHP to Perl to C++ to javascript, I still find myself coming back to VB6 for certain tasks, and that will continue to be true for a very long time.

      Feedback and Knowledge Base