I suggest you ...

12,075 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

    9533 comments

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

        @jeffery carlson

        VB .NET will never stick to the VB6 community ! this is the reality !

      • Dudica commented  ·   ·  Flag as inappropriate

        I am disgusted by the banning of Megan Winter's account on social.msdn.microsoft.com. She came with valid points for Visual Basic 6.0, too valid! And what the administrators do on a MICROSOFT site?! they erased the 60-70 valid comments ("Bring back Visual Basic 6.0 ! We all need it." issue) and banned the acount due to their inability to cope with the conversation! This is a disgrace for Microsoft! The admin that banned a perfect valid user like Megan Winter should not have access to this site !

      • Dudica commented  ·   ·  Flag as inappropriate

        I am disgusted by the banning of Megan Winter's account on social.msdn.microsoft.com. She came with valid points for Visual Basic 6.0, too valid! And what the administrators do on a MICROSOFT site?! they erased the 60-70 valid comments ("Bring back Visual Basic 6.0 ! We all need it." issue) and banned the acount due to their inability to cope with the conversation! This is a disgrace for Microsoft! The admin that banned a perfect valid user like Megan Winter should not have access to this site !

      • Dudica commented  ·   ·  Flag as inappropriate

        I am disgusted by the banning of Megan Winter's account on social.msdn.microsoft.com. She came with valid points for Visual Basic 6.0, too valid! And what the administrators do on a MICROSOFT site?! they erased the 60-70 valid comments and banned the acount due to their inability to cope with the conversation! This is a disgrace for Microsoft! The admin that banned a perfect valid user like Megan Winter should not have access to this site !

        "Bring back Visual Basic 6.0 ! We all need it."

      • axisdj commented  ·   ·  Flag as inappropriate

        Yes, it's really sad. MS has a bunch of vb6 programmers dedicated to continue to push their OS. Every copy of my software requires a new PC running windows, and yes we only sell a few thousand a year, but I'm sure there are many more like me.

        I think 2014 will be the make or break year, someone will come up with a vb6 replacement or MS will bring back vb6 and save their OS. The choice is yours MS. I know it takes resources to pull it off, but the ball is in your court, and the decision you make could very well seal your fate!

        PAY ATTENTION MS!!!

      • Anonymous commented  ·   ·  Flag as inappropriate

        I have been researching the last couple days. free pascal has caught my attention. free, open source, cross platform, inline asm, different calling conventions support, IDE seems quality on initial inspection. familiar to vb6 developer. Active development and community, many controls and samples, compatibility and independence core qualities they develop for.

        http://www.lazarus.freepascal.org/index.php

        MS is begging us to forget them, be careful what you wish for.

      • Luck Wolf commented  ·   ·  Flag as inappropriate

        yes, the guys from "Bring back Visual Basic 6.0 ! We all need it." on social.msdn.microsoft.com lack of character ! ugly! very ugly !

      • Megan Winter commented  ·   ·  Flag as inappropriate

        @Sten2005,

        on social.msdn.microsoft.com they were just cowards and powerless people, I did NOT make any spam ! They were not able to cope with the arguments so they simply banned me !!!!!!!!!!!!!!!!!!!!!!!

        This is a disgrace for Microsoft!

      • jeffery carlson commented  ·   ·  Flag as inappropriate

        I even gave the community enhanced VB.NET version the name VBX.NET (In favor of the early VB versions).

      • jeffery carlson commented  ·   ·  Flag as inappropriate

        Yes, Dudica I know what Iam talking about. But VB6 needs some major improvements to even be brought back as a real language like VB.NET. It would not even be named "VB6" if it was brought back anyways. As far as intelligence no, maybe some it had some quality but not intelligence. Can you by default use USB devices? (No, not unless you your a device driver developer which knows the HID.dll commands intimately). However, VB.NET can be improved and you can have your voice in the functions of it. I have a post here
        I started:http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/5575469-how-about-a-community-enhanced-version-of-vb-net-o

      • Dean commented  ·   ·  Flag as inappropriate

        Our company has recently hired two Vb.net devs to do VB6 and classic ASP

        hehehehehehehe

      • Dudica commented  ·   ·  Flag as inappropriate

        jeffery carlson we are talking about VB6 here. Come on, VB .NET will not raise at the quality and intelligence of VB6 ever !

      • Dudica commented  ·   ·  Flag as inappropriate

        @Anonymous votes speak, your personal opinion is irrelevant because it is malicious and has no connection with reality!

        Bring back the VB6 king !

      • Sten2005 - Microsoft support VB6 programming on Windows 10 until at least 2025 commented  ·   ·  Flag as inappropriate
      • Paul commented  ·   ·  Flag as inappropriate

        With all the billions at Microsoft why kill off a superb development platform as VB6. They did the same with Visual FoxPro - killed off at V9, and this will work with Win 8 as well.

        As they say, sort of bullet proof - you cannot kill them off - VB6 and VFP9 still live on.

        Why are Microsoft **** bent on forcing the development community onto VS2013 .net development is soooo awkward and the learning curve is exponential.

        Come on Microsoft spend your hard earned cash - Bring VB6 and Visual FoxPro into the 21st century, you will make the developer community very happy indeed.

      • jeffery carlson commented  ·   ·  Flag as inappropriate

        I think that vb.net should just have variant support which would half of the debate. Variants have been the biggest problem in upgrades. VB6 would not be useful now (outside of office) because a lot of functionality has been redone in VB.NET besides variant support. Anonymous is correct a new option to compile C# to native assembler adding vb.net and I would be hooked with the performance boost I get.

      Feedback and Knowledge Base