I suggest you ...

11,355 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…)
    EugeneEugene shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Sue GeeSue Gee shared a merged idea: On the 25th anniversary of Classic VB, Return It To Its Programmers  ·   · 
    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.  ·   · 

    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)
      • hugo from montrealhugo from montreal commented  ·   ·  Flag as inappropriate

        This thread reads like people trying to wage a holy war for others minds and steer their opinions. You are morons grow up. Vb6 is awesome I use it everyday but this helps no one this thread is useless. Just enjoy it as a gift while Ms slowly burns. Heck enjoy that too, they earned it. Bye to this thread.

      • AndreaAndrea commented  ·   ·  Flag as inappropriate

        No significant commercial software is written in C#.


        What C# was in Windows has been removed because it was too slow.
        Evernote used to be in C# but was rewritten in C++ for because C# was too slow.
        Some parts of Visual Studio uses C#, but Visual Studio is known to be slow.
        Even C# is written in C++.

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate


        Everyone (including most VB6 hardliners) will all convert to NET without any doubt, as it becomes the MOST POWERFUL development environment ever existed!!! And moreover, small teams and even individual developers have a great tool which is absolutely FREE!!! There is a huge future now for .NET. All the doubts vanished. Our team made the wise choice to choose .NET and WPF for our project a few years ago. We knew that we can not go wrong with XAML and NET in general. I am quite sure many VB6 fans will agree. Everyone is a winner. Regards.===>

        Microsoft integrates Xamarin into Visual Studio for free, will open source Xamarin runtime

        "Microsoft today announced that Xamarin is now available for free for every Visual Studio user. This includes all editions of Visual Studio, including the free Visual Studio Community Edition, Visual Studio Professional, and Visual Studio Enterprise.

        Furthermore, Xamarin Studio for OS X is being made available for free as a community edition, and Visual Studio Enterprise subscribers will get access to Xamarin’s enterprise capabilities at no additional cost. The company also promised to open-source Xamarin’s SDK, including its runtime, libraries, and command line tools, as part of the .NET Foundation “in the coming months.” Both the Xamarin SDK and Mono will be available under the MIT License. Speaking of the .NET Foundation, Microsoft also announced that Unity, JetBrains, and RedHat have all joined."

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate


        Dear VB6sters

        To be honest with you, I have used and actually learned programming using VB6 in the 90s. It was a great tool for a beginner in those days. It was a very good tool in it's days. I remember going through Planet Source Code in those days and finding useful hacks, whether it be subclassing or some weird multi threading hacks. I wasn't very familiar with modular concepts, factoring and OOP in those days and whatever I was writing was mostly patch code written by others. My programs were somewhat functioning but it was just a mess, a spaghetti code. The next time I was looking at my code to add up some functionality, I could not understand it and it would take me hours on end to figure what the heck I did before. Those are typical symptoms for spaghetti code. I am quite sure many others did write code similarly in VB6. I wasn't the only one for sure. You know VB1-6 was not created by considering modern modular design concepts. So from the beginning it was doomed. That's why it was promoting bad coding practices. The industy realized that. They couldn't effort to rely on single shot coder API hacks in order to get their mission critical programs to work. They needed a serious framework. So .NET was born.
        I am quite sure that you agree with me on this. This is NOT to undermine VB6. The fact is that VB6 can NOT be used in today's highly demanding programming environment. It will simply fall apart, unless huge renovations are made to it. Then one may raise the question. Why shall we update VB6 or more importantly how can we update it? It is almost certainly impossible to update VB6, as all the evidence shows that VB6 source code is not expandible and maintainable. VB6 was not designed to develop complex code. A new VB from scratch has to be designed. Well, then we are coming to the natural conclusion, There is a tool already been desined and it is called .NET, which is a complete re-design from scratch with managed code, garbage collection, OOP, multi threaded, with a huge native library etc. So, the request to bring back VB6 or to open source does not make sense, as there is already a well designed replacement for it.
        The above is just a logical deduction. It proves that VB6 is really not required any longer.

        Thanks and Regards

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate


        Whether or not .NET Native is used, freeing .NET applications from an operating system runtime fits better with today's development trends, for containerised applications and microservices, distributed applications built from components that can be maintained and updated separately.

        The cut-down Nano Server version of Windows Server runs .NET Core but not the .NET Framework; again it is all part of the move towards containerisation and DevOps, automated and continuous delivery of applications.

        Note that, UWP apps aside, .NET Core is for server applications, not desktop apps with a GUI. Microsoft is not porting frameworks such as Windows Forms or Windows Presentation Foundation to .NET Core. It is open source though, so it is always possible that the community may come up with GUI frameworks.

        There is also a relationship between .NET Core and Mono, the independent open-source .NET implementation founded by Miguel de Icaza back in 2001. Mono does support desktop applications. Now de Icaza is on the board of directors for the .NET Foundation, set up to oversee .NET Core. Speaking at the 2015 dotnetConf event in March 2015, de Icaza said that Mono may eventually be just a runtime core, borrowing both the "Roslyn" compiler and the CoreFx foundation libraries from .NET Core.
        The next question then: why cross-platform and open source? It turns out that these two questions are related. At dotnetConf, Program Manager Immo Landwerth described open source as the "most sustainable way to build a cross-platform stack." The reason given for going cross-platform is to attract new customers to .NET and build a stronger ecosystem, such as third-party libraries and applications that run on .NET.

        There are obvious risks for the company in both cross-platform and open source. Microsoft is giving away intellectual property as well as enabling customers to run .NET applications on non-Windows systems, with no revenue from licences.

        Internally to Microsoft, the business case for .NET Core always has to be made. Chatting to .NET Foundation folk I get the impression that this is all about Azure, Microsoft's cloud platform. Azure supports Linux as well as Windows, and if you deploy to Azure, Microsoft gets your money whatever operating system you use.

        A recently announced partnership with Red Hat would not have been possible without this open source, cross-platform strategy. Red Hat Enterprise Linux is now supported on Azure, and the "reference operating system for .NET Core on Linux", according to the press release.

        Another factor is that through .NET Core Microsoft hopes to stimulate use of its languages, including C# and F#, a functional programming language. If you code in these languages, Microsoft has a ton of libraries that will pull you towards SharePoint or Office 365, for example, so that the company can profit from licences or subscriptions there.


      • AndreaAndrea commented  ·   ·  Flag as inappropriate

        For web client development most things happen on the client side these days using JavaScript/HTML/CSS. And if you are using JavaScript on the client, it makes sense to use the same language on the server (node.js), particularly now most web servers use Linux not Microsoft.

        And even for mobile development, JavaScript or JavaScript/hybrid solutions are the way forward.

        Microsoft aren't really in this market, still being stuck with the bloated .Net which, despite Xamarin, only addresses the Windows desktop market.

        This suggestion allows VB to be transpiled to JavaScript, a quick and easy way for Microsoft to regain some relevance:


      • The CodistThe Codist commented  ·   ·  Flag as inappropriate

        "Given the extent to which it is still used..."

        Consider this: http://www.trendyskills.com/

        This site tracks the skills employers are looking for. The data comes from major job advertisement sites. Note that neither VB6 or VB.NET are on the graph. They're not looking for VB6 developers because they're not using VB6. It's just that simple.

      • paulpaul commented  ·   ·  Flag as inappropriate

        Microsoft say "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."

        Yet Microsoft make this difficult by not supporting the VB6 IDE.
        The VB6 Runtime is supported until at least 2025, so your existing VB6 apps continue to run.
        But even though the VB6 IDE installs and runs, Microsoft don't officially support it.

        It is time that Microsoft:
        . 1) Supports the VB6 programming IDE on Windows 7 & 10
        . 2) Allows a free download of the VB6 language and IDE

      • Jon AJon A commented  ·   ·  Flag as inappropriate

        I recommend this suggestion:-


        A really great idea. Classic VB6/VBA transpiling to JavaScript. Microsoft should do this.

        This would provide Web and mobile development for VB6 developers.

        This offers a way forward for existing developers of VB6 programming and should also tie in to the new JavaScript APIs in Office 2016.

      • LisaELisaE commented  ·   ·  Flag as inappropriate

        Me too. I wish I worked in an environment that allowed development PC's to access the Internet. For many of us those days are long gone.

        I would not mind exploring the CE version if they ever change that.

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        @Lofaday what you described is just VB6 par for the course. I lived it as you did and still break out VB6 on occasion. Though I too use .Net - VB6 is like a secret weapon to me.

        I wonder if some of the .Net ONLY guys are really insecure. The ones needing to keep posting false VB6 statements. Pro developers dont do this one another, so that leads one to the obvious conclusion...

      • mm commented  ·   ·  Flag as inappropriate

        "Microsoft: Windows 10 won't hit 1 billion devices by mid-2018
        Microsoft isn't going to make its self-imposed deadline of having Windows 10 installed on 1 billion devices by mid-2018, company officials have conceded."


        A liar, Microsoft, was a failure.

      • mm commented  ·   ·  Flag as inappropriate

        .Net dogs should think why No famous company in the world will use Microsoft's junk .net to develop products!

        .Net dogs should think why there is no good software in the world to use Microsoft's garbage.Net!

        Apple, Google, FaceBook, Amazon, Oracle, IBM...... alll will not use the garbage .net!
        Why?Because .net is the garbage, the guys only know the use of.Net is the garbage, these large companies will not employ such garbage!

      • mm commented  ·   ·  Flag as inappropriate

        Can anyone tell me in the world's big IT companies who only use.Net?
        No any one! why? Because.Net is rubbish!
        So .net dog @Gustavo Facchini @Gustavo Facchini @HMan....(These .net dogs are likely the same .net dog) must be in a very very small it company or a very very small company's it department!
        Why this .net dog can't work for big company? bucause .net dogs are all iintelligent low, now one will use it.

      • Lofaday - mail me on VB6 at QSL dot EULofaday - mail me on VB6 at QSL dot EU commented  ·   ·  Flag as inappropriate

        May I just stick my nose in here being once a frequent contributor. For what it's worth folks, obviously VB6 is outdated, but you are missing the point. It achieved the pinnacle of success because it adopted a paradigm that did not exist prior and has not been repeated since. It was pure RAD and ALSO able to produce very solid, professional apps. This paradigm was collapsed by MS because they could not see how to capitalise on it, and because of jealousy where MS developers (& their bosses) saw they were making millionaires (myself included) and were not getting the reward themselves. In the past, I backed these statements up and forgive me, I don't care to repeat myself continuously.

        I am now a consultant and STILL cracking out exceptionally fast and powerful sample apps with VB6. I then give those apps to irks like @LarsontheViking who are then charged with repeating the functionality in dot net. So far, they keep failing, and the directors keep choosing the software I put together in hours or days in VB6.

        @LarsontheViking -- "One of the big advantages of NET programming was that you could do things quicker, easier and cleaner". You are clearly from a very different planet to me, one swirling in delusional gases.

      • Vijay KumarVijay Kumar commented  ·   ·  Flag as inappropriate

        @Gustavo Facchini

        In my country (India) there is a growing interest in NET framework. People know that they can hardly find a job if they don't follow new technologies and VB6 is an old technology and mostly irrelevant. I am also a fan of Xamarin. With it we can design cross platform apps and now it is free as well.

      ← Previous 1 3 4 5 314 315

      Feedback and Knowledge Base