I suggest you ...

11,164 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)  ·   · 
    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)
      • AnaAna commented  ·   ·  Flag as inappropriate

        15 programming languages you need to know in 2015:

        1 Visual Basic 6.0
        2 Python
        3 Java
        4 Visual Basic .NET
        5 C#
        6 php
        7 Ruby
        8 Javascript
        9 C++
        10 Visual C++
        11 NASM
        12 Erlang
        13 Fortran
        14 R programming language
        15 COBOL

      • AnaAna commented  ·   ·  Flag as inappropriate

        Please bring back VB6. I will have nothing to do with .NET, an idiotic ill designed framework based on the over-usage of objects and classes, with a way too heavy syntax. In the past 17 years, I have written well over a million lines of code in VB3-4-6, all numerical computation, digital signal processing, mechanical analysis and 3d real time graphics. You will not find this code on PSC or the like, but in the engineering departments of major corporations, including all three biggest world-wide mining companies. Their requirements: something no-nonsense, easy for the typical dept technician (not much computer litterate) to handle and that works fast and into the long run. These companies don't like to jeopardize their investments in platform and software system changes.
        I expect the same from my programming tools. Formerly in C, much of this code works on par speedwise with their C originals, sometimes even faster. The native code generated by VB6 is truly top notch. I don't need nor use ADO (DAO is so easy and so much faster), XML, HMTL 5, Silverlight (another MS half-baked product gone deprecated) or any of the seemingly high level, flavour of the year tools, introduced recently and touted as the "next best thing" (for gullible .net techies anyway).
        There was .net 2003, 2005, 2008, 2010, 2012, 2013, now 2015. Don't go thinking they were ignored, on the contrary, I tried them all and I can write top notch code with them. But I will not. They are just failed, half-baked bloatware products that came out of the twisted micro-managing minds of software engineers with limited imagination and skills. All along the way, MS has been forced into marshalling just about anything legacy in order to make things work somewhat right.
        Is that all you (MS) can show for? Not productive at all. People want/need RAD. How long will this go on? It seems clear that developers at large (again with the exception of a few gullible techies) don't embrace the framework. There is no reason to. A change of course is required before it's too late. A. Einstein, a person known to have a few good working brain cells in his time defined insanity as : when you try something again and again and again, expecting somehow to get different results.
        Let's stick to what really works. A fast IDE that takes care of assembling all your programs into small, compact, fast executables with a minimal distributed runtime, boosted with easy and reliable access to GDI and other system level API's.
        The framework is ill designed technology. All it does is wrapping existing API's into a less usable form.The higher your depencies on wrappers, librairies and third parties, the bigger chances are your systems are going to fail with no solution in sight. I have been that road too many times before. With such people as Paul Yuknewicz at the wheel, the confidence in MS as a software company has been shattered possibly to the point of no return.
        P.S. I don't mind the .net techies and trolls spamming this thread. They have no credibility whatsoever.

      • AnaAna commented  ·   ·  Flag as inappropriate

        Please bring back VB6: a comment by Anonymous

        Once again : lies, half-truths, false assumptions, bad mathematics and attacks on character are the normal arguments of the .netties. It's kind of a "framework" of mind. They like to live their own facts free life in their little yet bloated OOP fantasy world, being rocked by inheritance and polymorphism.
        The truth is MS is exercising vote censorship on the most popular idea EVER in uservoice, denying thousands upon thousands or programmers being given a voice. They just don't listen anymore.
        We don't like/want the framework or .NET. Please bring back VB6.

      • AnaAna commented  ·   ·  Flag as inappropriate

        .NET disciples show us your code !

        "Again, the >NET disciples here, that are insulting any vb6 users intelligence please show us your superior products/ growing companies / growing profits."
        They can't.
        These trolls who post their .Net .Nonsense are just low paid coders who have to do what they are told. They have no choices, they are not decision makers, it is doubtful they have ever written a full application - they just write small parts of someone else's apps.
        They don't even have any ideas of their own. They just copy and paste what others have said.
        Expecting them to be able to show anything they have done themselves is setting the bar far too high.

        Best regards,
        Anthony Green

      • AnaAna commented  ·   ·  Flag as inappropriate

        Anonymous commented on uservoice.com
        I firmly believe people still using VB.NET are mostly lazy, incompetent, self-centric people without having technical capabilities to see the depths of modern software technologies. They are stuck at primitive old fashioned world like VB.NET and out of fear and incapacity of advancing themselves, they try bashing wonderful technologies like VB6. By doing so they radiate the deep fear that they have in themselves and instead following new technologies, they want the world change to their unfounded and shallow ways of thinking. They are bunch of pathetic and pitiful people, without any serious software knowledge. I am sure of that, as I don't see any of these people here able to get involved in any intelligent conversation to prove that they understand what software is.
        ====>L A Z Y
        ====>I N C O M P E T E N T
        ====>S T U P I D

      • ░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░ commented  ·   ·  Flag as inappropriate

        Rob Leedic talks about the massive advantages of VB6 vs. VB.NET
        I'm not trying to debate on the economics of the issue, just the common complaint that MS did all of this to make money from developers. The only mistake MS made was thinking that all VB6 developers wanted an insecure, crowded and slow language like VB.NET (some did).
        It's also not about taking the easy road. My VB6 code is far more complex than anything that I was ever able to produce in VB.NET, or ever would have been able to. The difference is I don't have to worry about silly things like formatting code, or moving controls around a form for different resolutions, I can focus on more important things. Just because something is hard or easy doesn't make it right or wrong. Some of the things that make VB6 easier also help produce better code by producing less, and less replication.
        For me, the long and short of all of this is that my VB6 programs are faster, leaner, and have a far better feature set than my VB.NET versions ever could. This all benefits my end user.
        Just because a portion of the VB6 community didn't migrate, doesn't mean the MS missed the mark. Frankly the greater VB6 community is massive, and far overshadows any prior MS community.

      • ░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░ commented  ·   ·  Flag as inappropriate

        VB6 paradigm is not only the present but also the future
        Jeff I.
        Freelance Software Developer/Consultant/Certified oDesk Contractor
        Let's look at it this way. Ultimately, everything has to run on a machine. Open source? That's a paradigm not a programming technology. As far as VB6 goes, the syntax is the heart of the matter. As we move into the future I think this paradigm is going to be an absolute necessity. Whatever the future holds as far as programming techs go, I think they're going to get higher level requiring that there be some intermediate compilation from a high level programming tech to some intermediate state and ultimately down to machine language so it can be executed. We already have that VB6. That's what it's all about. So yes - I think that VB6 is going to be with us for a long time. Any successor will be designed according to the VB6 paradigm by necessity. I'm not the biggest Microsoft fan, but I do think that the VB6 paradigm is not only the present but also the future.

      • ░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░ commented  ·   ·  Flag as inappropriate

        VB.NET seemed to be a toy compared to VB6: by Cristi (PhD in mathematics)
        We started our company which designs high end software solutions in the beginning of 2000s. In those days .NET was new and many people were using VB6. We had to make comparisons to choose our platform. We opted for VB6, as the advantages over .NET was huge. VB.NET seemed to be a toy compared to VB6 and not to mention VB6 was just a fraction of what is VB6 today. Glad we made the right choice. Today we have no problem with maintaining, advancing and expanding our code and we run a successful business with tens of thousands of clients using our VB6 based solutions.

      • ░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░ commented  ·   ·  Flag as inappropriate

        What does the future hold for VB6? Looking for 5-10-20 years into the future. Do you think VB6 will still be an important player in the technology world? why?
        Gavin S.
        Founder / CTO at Solid Cloud, LLC
        To me using Visual Studio 6.0 vs other Visual Studio tools there is no comparison. This is much like asking a graphics designer to create graphics in Photoshop vs Paint. As Software Development continues to become more like Engineering, these tools will become more and more important. I'm sure PHP / javascript will be the same today as they will be in 20 years, but I'm pretty confident we'll be another 2 levels of abstraction higher on the MS toolset. In the end, there is no comparison, and no better toolset for developing software than Visual Basic 6.0, Visual Studio 6.0 in general.

      • ░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░ commented  ·   ·  Flag as inappropriate

        Martin Phillips says

        I think you people have to realise that .NET and VB.NET is dead and it's not coming back.
        Microsoft has no reason to bring it back.
        Most of the people who learnt VB.NET are now too old to coding professionally.
        The coding world has moved on with classic VB (VB6) and those it left behind were left behind because they were not intellectually capable to realize the pardigm.
        I and many others were, however, capable of adapting VB6 to this change. We use VB6 and love it!
        So I'm sorry for you people who are unable to evolve (or follow MS like a sheep) - such is the nature of life. Only the strong survive. You just have to deal with that.
        VB.NET is dead and it's NEVER coming back!

      • MichaelMichael commented  ·   ·  Flag as inappropriate

        Wow you killed a lucid request (from Mary) without any explanation and it de-evolves to mud slinging. This is completely expected when one group is completely ignored at the expense of another. Both could thrive if you would allow it.

        This is like watching a slice of humanity. => When it does not work.

        .Net guys are you looking? This is YOU too in time...unless MS have a inner revolution.

      • ░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░ commented  ·   ·  Flag as inappropriate

        The VB6 man commented · March 29, 2015 07:12
        ………….……………………. „-/*"\„,„,
        …….…………………….¸„-^"¯ :\_ / o '"*'"¯/' WOOF WOOF
        ……………………¸„„-^"¯ : : : : : : : : ¸„,-~"
        **¯¯¯'^^~-„„„----~^*'"¯ : : : : : : : : : :¸-"
        .:.:.:.:.„-^" : : : : : : : : : : : : : : : : :- VB6 PEOPLE ! GIVE THIS CUTE DOG
        :.:.:.:.:.:.:.:.:.:.: : : : : : : : : : ¸„-^¯ TO THE .NET PEOPLE ! TO SHOW
        .::.:.:.:.:.:.:.:. : : : : : : : ¸„„-^¯ THAT WE HAVE ... CONVERTED TO .NET !
        :.' : : '\ : : : : : : : ;¸„„-~"¯
        :.:.:: :"-„""***/*'ì¸'¯
        :.': : : : :"-„ : : :"\
        .:.:.: : : : :" : : : : \,
        :.: : : : : : : : : : : : 'Ì
        : : : : : : :, : : : : : :/

      • ░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░ commented  ·   ·  Flag as inappropriate

        /▌ ░ ░A░T░T░E░N░T░I░O░N░
        / \
        ☻۶░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░
        / \
        ☻۶░ ░C░O░N░V░E░R░T░░T░O░░ .░V░B░6░ !░ !░
        / \
        ☻۶░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░
        / \
        ☻۶░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░
        / \
        ☻۶░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░
        / \
        ☻۶░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░
        / \

      • ░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░░ ░V░B░6░░I░S░░T░H░E░░ F░U░T ░U░ R░ E░ commented  ·   ·  Flag as inappropriate

        Derbedeu commented • March 6, 2015 9:25 PM •
        "Look at the 15 languages I have listed below. "
        Look at the comments listed below that list. Lists like this will put Microsoft in total obscurity and irrelevance if VB6 is not back !
        PS: http://vb6awards.blogspot.com/2015/03/why-microsoft-net-failed-and-visual.html
        Anonymous commented • March 6, 2015 9:19 PM •
        I look at youtube and it is filled with Visual Basic 6 tutorials. Many rankings put VB6 on the first place:

      ← Previous 1 3 4 5 213 214

      Feedback and Knowledge Base