I suggest you ...

11,219 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Dr. Mihai Bush, PhD (MPV)Dr. Mihai Bush, PhD (MPV) shared a merged idea: Make Visual Basic 6 as a part of Windows (by default)  ·   · 
    Luis Fernando Echeverri LozanoLuis Fernando Echeverri Lozano shared a merged idea: VB6 Honoris Causa  ·   · 
    Anonymous shared a merged idea: Please bring back Visual Basic 6.0 !  ·   · 
    Anonymous shared a merged idea: The silent majority of VB6 users did not ask VB.NET  ·   · 
    MaryMary shared a merged idea: Merge the core of VB6 into Office or the Windows OS.  ·   · 
    BravoBravo shared a merged idea: Bring back Classic Visual Basic, an improved version of VB6  ·   · 
    HMan2828HMan2828 shared a merged idea: Make a new Classic Visual Basic, an improved version of VB6  ·   · 
    Ana-Maria (VB6 software programmer)Ana-Maria (VB6 software programmer) shared a merged idea: Bring back Classic Visual Basic 6.X, an improved version of Visual Basic 6.0  ·   · 
    Anonymous shared a merged idea: Bring back Classic Visual Basic 6.X, an improved version of Visual Basic 6.0  ·   · 
    Marius OrionMarius Orion shared a merged idea: Bring back Classic Visual Basic, an improved version of Visual Basic 6.0  ·   · 
    PacManiPacMani shared a merged idea: Close the suggestion to "bring back VB6"  ·   · 
    VB6 FireVB6 Fire shared a merged idea: Bring back Classic Visual Basic, an improved version of Visual Basic 6.0 (the old idea has been stoped at 7400 votes for no good reason)  ·   · 
    MeredithMeredith shared a merged idea: Make VB6 Free  ·   · 
    Mike PaulickMike Paulick shared a merged idea: Bring back VB6. I have no interest in .net. VB6 is better for me.  ·   · 
    David KayeDavid Kaye shared a merged idea: Bring back VB 6.0! It's an extremely handy language used on tons of business apps.  ·   · 
    Adam SpeightAdam Speight shared a merged idea: Don't do a Classic VB (VB6). Open Source the VB6 compiler source code.  ·   · 
    VB6 FireVB6 Fire shared a merged idea: Bring back our un-killable cockroach, is ours !  ·   · 
    Nitesh PatelNitesh Patel shared a merged idea: The Old classic visual basic 6.0 bring it back  ·   · 
    I_A_WI_A_W shared a merged idea: Visual Basic 6.0: A giant more powerful than ever  ·   · 
    Anonymous shared a merged idea: Full vb6 Compatiablity, dammit  ·   · 
    your nameyour name shared a merged idea: shove .net up your boss's butt. bring me VB6-A already.  ·   · 
    Anonymous shared a merged idea: Open Source VB 6  ·   · 
    leoleo shared a merged idea: make it easier. In VB6 i don't have to know what classes are. It has been to complicated for simple programms.  ·   · 
    declined  ·  Visual Studio TeamAdminVisual Studio Team (Product Team, Microsoft) responded  · 

    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
      I agree to the terms of service
      Signed in as (Sign out)
      • axisdjaxisdj commented  ·   ·  Flag as inappropriate


        I read somewhere the following: "The difference between a terrorist and a Object-Oriented Methodologist is that you can try to negotiate with the terrorist". A lot of people that behave like you describe in this post make it come true :o)

      • dotNetRulezdotNetRulez commented  ·   ·  Flag as inappropriate

        MS could give the world an early xmas present and place VB6 into the public domain man. Imagine that! VB6 for free for everyone. Whhhaaaat! Peeps be lov'n them if they did that.

        Do it MS. I dare ya!

      • Jon McRaeJon McRae commented  ·   ·  Flag as inappropriate

        Been programming 25+ years. I got no issues with VB6 as a language. I use new and old languages as I need'm.

        I like that VB6 is not a language that looks like coNtrol charActers too. Might as well program in Perl if you want that!!!

        On that topic VB6 apps are actually enjoyable to write. C, Perl and those type languages I do but they are more of a chore.

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        Would you like to try an experiment? As I prepare my next Oracle book and new revs on other books on various software languages it would really be no trouble to create a "VB6 for Windows 10" eBook.

        I can see from my Google Adwords Campaign for instance that my Oracle site got 80,000+ impressions in the last month. I can also see how may of those clicked and went to my site. The volume of stats Google provides is incredible. What words they searched on connecting to what links etc.

        I can do the same with VB6. This would give us some cold hard numbers that would be really hard to misinterpret by even the most polarized.

        The thing is, the code elitist have their .Net. The world has VB6. It is\was created in the spirit of letting EVERYONE create. Sure new programmers write non-ideal code. Didn't we all at some point? No stopping anyone from using Java or .Net too. Better to know more languages than less we all seem to agree on.

        Alas, what keeps long term developers well versed in multiple languages coming back to VB6? ;-)

      • ThomasThomas commented  ·   ·  Flag as inappropriate

        Not buying it hman. **** software comes in all flavors. If you got stuck supporting something you didnt enjoy its on you for taking the job and for then sticking with that gig. There is plenty of different types of work for a skilled developer to choose what they do want. A holier than thou, caustic attitude is not productive. Out of all the languages I work in, I specifically choose VB6 for most tasks as it best fits my needs.

      • HManHMan commented  ·   ·  Flag as inappropriate


        The problem is not regular Joe's solving their own problem, it's those regular Joe's then marketing their half assed fix as acceptable software... I have seen some atrociously bad code in my time, and probably over 75% of it was VB6. Sure, not all VB6 code is inherently bad code, but even great VB6 code HAS to incorporate bad code and bad structure, because that's just how the language is.

      • HManHMan commented  ·   ·  Flag as inappropriate


        The problem is that competent software engineers and programmers are still stuck today supporting unmanageable VB6 code messes because people who can't be bothered to learn something better keep saying they love it and it's great. Or because ****** managers don't see further than right now and see updating as a costly maneuver with no point. Your ****** language wrecks our days and kills our fun. That's why I and others hate VB6 to the core, especially BECAUSE it allowed people who have no business making software to market ****** applications.

      • ThomasThomas commented  ·   ·  Flag as inappropriate

        You know I dont wear cow boy hats, but I dont go around telling people they have no use and are dumb. I have never understood why people go so far out of their way to talk down on vb6. If its not your cup of tea, thats cool, go do your own thing. And one of the beautiful things of vb6 is that you didnt have to be a professional programmer to be productive in it. Regular joes could use it to solve their day to day problems. It enabled people to be creative and productive.

      • JillJill commented  ·   ·  Flag as inappropriate

        >> If you don't know at least 4-5 languages today, you aren't a programmer.

        Check: I know and use about a dozen.

        >> And if at least one of those isn't .NET related, then you aren't programming for Windows.


        I work in a very diverse environment jumping from one lang to another all day. VB6 is very easy and quick to make changes in. Soild as a rock. Matlab, LISP, .Net and JSP all fine too. Whatever.

        I dont think it is the language that makes one a professional but what one does with the language any particular environment mandates. As far as languages go VB6 is fine. Nothing I have not been able to do in it thus far.

      • FreddyFreddy commented  ·   ·  Flag as inappropriate

        One other thing that would give the thought more pull would be to start with a professional PR company. Then you could start the crowd source campaign with a quote in hand from a reputable company and people would have faith that the money was going to be managed and put to use in a solid way. Maybe you dont get the full on open source, but you keep vb6 ringing in thier ears and something they cant dismiss and it in new developers minds to ask about. Maybe as time goes on and its only the hardcore guys left who believe in it and who write solid software any old stigma about the language will be left behind and people have to accept it is a good language that absolutely has an appropriate business use. You never know what is going to work, you can only keep trying and watch. If you just give up then you can be sure you get nowhere. I like lazarus, and have contributed some to the project, but it really needs solid ActiveX integration so I can use my libraries.

      • HManHMan commented  ·   ·  Flag as inappropriate


        That FooBasic thing is just some code generator for ASP.NET! Why wouldn't you learn ASP.NET instead and learn something you actually will reuse? If you are going to learn something anyways, seems pointless to avoid the proper language for a lazy hack.

        As for the rest of you talking about press releases and billboards, you are completely deluded by your pipe dream. VB6 is dead and will stay dead. No one wants to or has the resources to, or even should attempt to revive it. If you don't know at least 4-5 languages today, you aren't a programmer. And if at least one of those isn't .NET related, then you aren't programming for Windows. Period.

      • axisdjaxisdj commented  ·   ·  Flag as inappropriate

        What MS thinks or says does not matter as much as what the public thinks, Yes vb6 guys are looked down upon, but as of recent years more and more really smart people have come out and talked against the cult thinking OOP that vb6 is not supposedly capable of and makes it inferior in their eyes. The world is changing, the oop cult thinking trend is loosing steam, and if our press release along with billboard brings to light these arguments not from us, but from others, our impact will be big.

      • Anonymous commented  ·   ·  Flag as inappropriate

        > Having most of MS employees see a message from us every day for 30 days, hardly seems like a waste.

        All MS would have to say in response is the sort of thing that Paul Yuknewicz wrote above and everyone would nod in agreement.
        In the wider development community, vb6 coders are looked down on as code monkeys or worse and a stunt like this would only add to the view that we're out of touch with reality and maybe a little bit crazy.
        Nobody cares what we want except us.

      • EdEd commented  ·   ·  Flag as inappropriate

        Its like a company invents say THE WHEEL! For chariots and wagons etc. Then some of the drivers say we can make it better for Object Oriented drivers. So the next version bind bricks to the wheel and also make sure it is not compatible with all the other chariots used before this new version.

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        We never know what our efforts here truly effect and who sees them. That we would know. Especially if we can also get local (or global) media involved to place them in a position to explain why they neglect this demographic that wont go away.

      • axisdjaxisdj commented  ·   ·  Flag as inappropriate

        We could also consider a Facebook campaign to MS emplyees only, but that may be less effective

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        Funding a VB6 billboard that the majority of MS employees would have to see on their commute each day to work...

        I'm in!

      • axisdjaxisdj commented  ·   ·  Flag as inappropriate

        All advertising has the potential of being a waste. Having most of MS employees see a message from us every day for 30 days, hardly seems like a waste. especially for 5k.

        It does not guarantee anything, but it is better than what is happening now.

        All other efforts require a much bigger investment and are much less likely to succeed, baby steps to the goal is my thought.

      ← Previous 1 3 4 5 240 241

      Feedback and Knowledge Base