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)
      • uleysees commented  ·   ·  Flag as inappropriate

        Microsoft is hurting big time. With the horrendous Windows 8 interface and the changes made to Office and other programs, its no wonder they've become irrelevant.

        Time to step up Microsoft. Open up VB6 or update it. Bring it up to today and support it.

        DEVELOPERS are what made you great and developers will be your undoing if you're not careful.

      • Anonymous commented  ·   ·  Flag as inappropriate

        It's been 16 years now without an update.
        I'm grateful to microsoft for maintaining support for vb6 applications.
        But all this time I've been working in vb6 while worrying about the future.
        Please Microsoft, either opensource vb6 or give us vb7
        I would pay MS $10,000, but it's really unfair to leave us in this undead zombie place

      • Frank commented  ·   ·  Flag as inappropriate

        I use still VB6 for big production solutions in the pharmaceutical industry on with Win 7 clients and Oracle Databases -> no problems.

        Make a little update for 64 Bit and I'm happy -> VB7 Classic!

      • Alex Krymov commented  ·   ·  Flag as inappropriate

        Only foolish parents can forget their responsibility for their children and generated deprive them of parental attention and support
        Encourage responsible gentlemen from Microsoft to think again and to fully implement its previous commitments to its historical multiple customers, developers and users of the products created by the classic VB6
        The only way to keep the faith in the good intentions and Microsoft face

      • ccc231 commented  ·   ·  Flag as inappropriate

        @Leonardo Azpurua: very well said: "The responsibility of the software providers (be them application or OS developers) is to provide compatibility to safeguard their customers investment. Failure to do so is breaking any imaginable ethical principle.

        The demise of VB6 has shattered the image of Microsoft to a point beyond belief. What software provider with a grain of common sense provides an update that renders unusable their users' data?

        If they ever bring back VB6, or however they wish toname a new tool that accepts my current VB6 projects and produces executable code with the proper behaviour, they will certainly recover my interest and have me as a satisfied (albeit cautious) customer."

        Otherwise, I will continue to regard them as just a flock of corporate scammers.

      • Sergey commented  ·   ·  Flag as inappropriate

        @Leonardo Azpurua: ok.
        @All: Support COM.32/.64 and ligaments with dll API .32/.64 cost utra expensive as most Microsoft and every developer who is used to VB6.32.
        If you are in the program ispolyuzuete At least one COM component or dll library .32, then go to .64 no longer happen.
        And you just want to keep older components that are only .32.
        Furthermore, the addition of .64 immediately force you to become expert of programming at the same level as an expert C + +.
        Investment by migrating to .64 would cost dear to you.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I feel sorry that C programmers can still choose between native and managed apps, while VBs have only a managed path!!!

      • Anonymous commented  ·   ·  Flag as inappropriate

        I Love VB6, I use it on Windows 7, Even though I took a course on Visual Basic .NET I prefer and use VB6 I can not stand the .NET garbage

      Feedback and Knowledge Base