I suggest you ...

11,355 votes
Vote
Sign in
Check!
(thinking…)
Reset
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

    6715 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • paulpaul commented  ·   ·  Flag as inappropriate

        VB6 Common Controls replacements

        These are replacements for the Microsoft Common Controls without using OCXs.
        They support the latest API calls, functions, properties and visual styles (themes).

        The controls have similarly named properties and methods and many of them have some new ones as well.
        Unicode is supported and the controls are DPI aware. There are no dependencies.

        http://www.vbforums.com/showthread.php?698563-CommonControls-(Replacement-of-the-MS-common-controls)

      • Anonymous commented  ·   ·  Flag as inappropriate

        And i think they know that .net suxx and just want to stay on her seats. They have releasesd VBA64 bit. And that is most of the things you need to build a vb6 compiler. Cause its just a wrapper.

      • MikeBMikeB commented  ·   ·  Flag as inappropriate

        @Pritesh

        "Java is such a ****** implementation of OOP, and C++/C# followed its lead. Perhaps if SmallTalk (or Ruby) had become the big OOP languages things would have turned out better (albeit still imperfect), but as things are it is hopeless. "

      • Anonymous commented  ·   ·  Flag as inappropriate

        We understand that Microsoft need to change things for future application development, just think about those programmers crossed the age of re-learning and programming, how they can manage things. What about small applications which not demands cross platform compatibility? I think Microsoft must go for improved version of VB6 for those who just want to be simple developer.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        Scott Hanselman demonstrates how to use the DesktopAppConverter to deploy a VB6 application to the Windows 10 Store with no changes in his blog post:

        Putting (my VB6) Windows Apps in the Windows 10 Store - Project Centennial
        http://www.hanselman.com/blog/PuttingMyVB6WindowsAppsInTheWindows10StoreProjectCentennial.aspx

        Very interesting article; obviously apply to more app types and not just VB6.

      • mm commented  ·   ·  Flag as inappropriate

        I have a prediction:
        1 Microsoft will die before 2025, and will be acquired by other company, and then vb6/vc/winform/wpf/silverlight... will be open sourced by the new company, these Microsoft abandoned desktop technologies will get better development in the form of open source.

        2 The garbage technology UWP will be completely dead, because webassembly will be mature, webassembly is more suitable for the new web/ mobile.

        So, don't waste time to rewrite your software to the .net or to UWP.
        If you want rewrite your software, you should waite several years after webassembly be more mature.

      • mm commented  ·   ·  Flag as inappropriate

        The .net core is born for UWP and web.

        The old .net is dead, because microsoft force everyone to transfer from the gabage .net to the gabage UWP.

        So microsoft proved the .net is gabage, now we know UWP is gabage too, so everything from microsoft is gabaga.

        So don't waste any time on microsoft.

        Microsoft is dying day by day.

      • mm commented  ·   ·  Flag as inappropriate

        bknight721 11 HOURS AGO
        Note to MS: I view your entire UWP platform as trash. Nothing more than dumbed down little kiddie apps designed for the phone that Daddy bought for them. No way would I ruin any of my perfectly good desktop programs by converting them to this junk.

        http://www.zdnet.com/article/microsoft-to-make-desktop-bridge-more-readily-available-to-win32-developers/
        ---------------------------------------------------------
        As i have said, .net is gabage, and now other people has proved UWP is gabage too.
        Today, microsoft want kill the gabage .net and force everyone to transfter from the gabage .net to the gabage UMP.

        Everything from microsoft is gabage.

      • HManHMan commented  ·   ·  Flag as inappropriate

        Did I win something? I heard my name and came back running...

      • Grant SwingerGrant Swinger commented  ·   ·  Flag as inappropriate

        Ok, I'll bite. How does 6,700 posts, a big chunk of them nonsense posted by trolls on both sides, constitute a reason for MS to spend the money to bring back a virtually dead language?

      • Celebrate VB6 programming and VBA programmingCelebrate VB6 programming and VBA programming commented  ·   ·  Flag as inappropriate

        6,700 posts !

        Microsoft, now is the time to look again - either update or open source VB6.

        Well done everyone.

        Special thanks to Hman and multi-username Zagor for all their efforts to support VB6 programming and VBA programming in this thread.

      • PriteshPritesh commented  ·   ·  Flag as inappropriate

        Goodbye, Object Oriented Programming

        The author of this article says...

        "I was gung-ho to leverage the benefits of Inheritance, Encapsulation, and Polymorphism. The Three Pillars of the Paradigm.
        I was eager to gain the promise of Reuse and leverage the wisdom gained by those who came before me in this new and exciting landscape.
        I couldn’t contain my excitement at the thought of mapping my real-world objects into their Classes and expected the whole world to fall neatly into place.

        I couldn’t have been more wrong."

        Goodbye, Inheritance.
        Goodbye, Encapsulation.
        Goodbye to OO Polymorphism and hello to interface-based Polymorphism.

        Good-bye, Object Oriented Programming.

        https://medium.com/@cscalfani/goodbye-object-oriented-programming-a59cda4c0e53#.tc8yny3ka

      • paulpaul commented  ·   ·  Flag as inappropriate

        B4X is a set of VB-like RAD development tools.

        B4A is for development of Android apps.
        B4i is for development of iOS (iPhone, iPad) apps.
        B4J is for cross platform desktop, server and IoT solutions on Windows, Mac, Linux and Raspberry Pi.
        B4R is for Arduino development.

        B4J and B4R are free.

        Well worth a look. https://www.b4x.com/

      • ErelErel commented  ·   ·  Flag as inappropriate

        @MicahelE check the B4X suite: https://www.b4x.com

        A RAD tool based on vb language (not identical) that supports: Android, iOS, desktops, servers, Raspberry Pi, Arduino and more.

      • paulpaul commented  ·   ·  Flag as inappropriate

        @Microsoft support VBA programming

        As a solution for VBA programming in Office 365 this would be good. Office 365 doesn't support VBA programming, it has JS instead.

        So the great Office feature of recording VBA macros is lost. This suggestion could allow VBA macros to be transpiled to JS.

      ← Previous 1 3 4 5 335 336

      Feedback and Knowledge Base