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

        Jetbrains 2018 survey.

        Programing languages learning/learnt in last 12 months

        1) Python
        2) JavaScript
        3) Java
        4) Go
        5=) Typescript
        5=) Kotlin

      • Anonymous commented  ·   ·  Flag as inappropriate

        Jetbrains 2018 survey.

        Primary Programming languages

        1) Java
        2) JavaScript
        3) Python

      • Anonymous commented  ·   ·  Flag as inappropriate

        Jetbrains 2018 survey.

        Top programming languages

        1) JavaScript
        2) HTML/CSS
        3) Java
        4) SQL
        5) Python

      • Anonymous commented  ·   ·  Flag as inappropriate

        Yes, VB.Net should never have been invented. It failed in its aim of replacing VB6 and has been in a long term decline.

        Just like C# failed in its stated aim of overtaking Java, and it too is now declining.

        Old languages for old times, they just haven't kept up with todays requirements.

        That's why there are only 1.8 million C# developers, 180,000 VB.Net developers and 18,000 F# developers.

        Meanwhile Microsoft jumps on every bandwagon to try and keep .Net afloat. A few months ago Xamarin was going to be the saviour of .Net. Then .Net Core. Now WebAssembly is the new messiah. Next month something different.

        .Net is just legacy now. But there will be plenty of maintenance work to keep old applications running, and keep the fanbois happy.

      • Joe Bolton commented  ·   ·  Flag as inappropriate

        Look at the long term picture. Scroll down to the Very Long Term History table on the Tiobe page. For C# we get:

        2003: 8th
        2008: 7th
        2013: 5th
        2018: 5th

        BTW, that sudden spike in popularity around 2012 does not show up in any other language index.

      • Anonymous commented  ·   ·  Flag as inappropriate

        C# declines from 4th most popular language in 2017 to 8th most popular in 2018.

        VB.Net declines from 13th most popular language in 2017 to 18th most popular in 2018.

        F# isn't used enough to be counted.

        For the sixth year in a row, JavaScript is the most commonly used programming language.

        JavaScript frameworks node.js and Angular are the most widely used frameworks.


      • Anonymous commented  ·   ·  Flag as inappropriate

        >>Microsoft never claimed 1.8Million Net users. This is your invention. Below, Microsoft video shows over 10 Million VS VCode users. Considering that over 90% of VS and VCode users are also using .NET, it means around 10 Million .NET users.

        Fake news

        Microsoft claim 2 million .Net users, 1.8 million C# users, 180,000 VB.Net users, 18,000 F# users.

      • Anonymous commented  ·   ·  Flag as inappropriate

        No one will be interested to bridge VB6 apps into Windows 10 Store. The main reasons are simple.

        1-There is nowadays no commercially successful legacy VB6 product to convince anyone to purchase it, even if you convert it to Windows Store. So no one will bother to create a bridge for that. It would be a waste of time.
        2- You have to lift up the archaic UI of VB6 apps, before putting it on the Store, which would be challenging with all the mangled spaghetti code behind. Good luck with that.
        3-VB6 is the most hated platform according to Stack Overflow for 3 consecutive years. Who will bother to do the bridge? The "geriatric appreciation society" of VB6sters here? LOL.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Microsoft never claimed 1.8Million Net users. This is your invention. Below, Microsoft video shows over 10 Million VS VCode users. Considering that over 90% of VS and VCode users are also using .NET, it means around 10 Million .NET users.

        "Put up or Shut up!!" LOL.

        But no matter what, you won't get over your dogmatic beliefs. In your toxic mind you think VB6 is still popular with millions of users, while the surveys show otherwise.

        ===>Check this out

        For the THIRD year in a row, Visual Basic (for 2016-2017-2018, Visual Basic 6, specifically) ranked as the most dreaded language. Most dreaded means that a high percentage of developers who are currently using the technology express no interest in continuing to do so.
        Visual Basic 6
        79.2%.........FOR THE REST ==>https://stackoverflow.com/insights/survey/2017/?utm_medium=email&utm_campaign=dev-survey-2017&utm_content=em-features&utm_source=so-owned



      • Anonymous commented  ·   ·  Flag as inappropriate

        >> ASP.NET just got a big boost from Microsoft!!!

        Top Web Development Frameworks 2018

        1 Angularjs
        2 Laravel
        3 React.js
        4 node,js
        5 Ruby on Rails
        6 Symfony
        7 ASP.NET
        8 Yii
        9 Meteorjs
        10 CakePHP

      • Anonymous commented  ·   ·  Flag as inappropriate

        Latest data proves that there are over 20 MILLION .NET users!!! So the claims here by Microsoft that there are only 1.8M .NET users is a bogus, BS and outright Lie.

        Also Popularity of C# stands at 64.4 (up this month).

        C# will soon be one of the top 10 languages in Stack Overflow.

        No negative-propaganda against .NET can change this fact. Only .NET haters will resort to this type of tactics and false claims.

      • Anonymous commented  ·   ·  Flag as inappropriate


        >> "I have zero desire to lick your vegemite sandwich"

        I suggest you ask an adult to explain this phrase to you. You may then wish to reconsider using it.

      Feedback and Knowledge Base