I suggest you ...

11,155 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…)
    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

    4585 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...
      • NigitNigit commented  ·   ·  Flag as inappropriate

        more than 22 open source programming languages were made in Visual Basic 6.0.

      • EdwardEdward commented  ·   ·  Flag as inappropriate

        >> I agree with Chuck, this will be right time to bring it back!

        I agree too. A sound business case can be made from Chuck's statement. Brilliant!

      • ChuckChuck commented  ·   ·  Flag as inappropriate

        Lots of folks wonder why MS moved away from VB6 (or as they say moved on). I think the decision was partnered with the profession of programming. VB from beginning to VB6 made windows programming accessible to almost anyone. Not toss away programs but science and business all the way up to corporate and industrial type programs. A VB6 programmer didn't have to be a computer science graduate or have any MS programming certificates to make a living coding real world money making apps. In fact VB6 enabled the client to also be the programmer. A tool like that was clearly a threat to the programming community. MS would rather relegate "anyone programming" to useless programming using SmallBasic.

        All I read currently is how MS needs a win for Windows 10 and for that they need a large user base to (thus the free upgrade) to inspire developers to make programs for Windows 10. I think MS fails to realize what made Windows great (in in many cases indispensable) in the past (and even now) was the vast world wide use of VB6 and the many "novice" and professionals programming windows apps because of not only the RAD but the ability to scale from RAD all in the same VB6 IDE.

        MS needs an active novice to professional development platform again and it would do well to bring back VB6 with some enhancements to work in 64bit and with the new OS 7-10.

      • Anonymous commented  ·   ·  Flag as inappropriate

        [Translated with Google Translate]

        Once upon a time, long ago I started programming in GWBasic. Pretty soon I discovered TurboBasic. After a while I found a Visual Basic 3. Then there were new versions of Visual Basic-a. After version 6.0 came out versions of .NET. I then stopped my desire to learn the next version. While creating the program was pleasantly automated so much new syntax somehow to me he has not arrived. I find it unpleasantly was associated with earlier attempts to get to know other programming languages, "holy", Pascal and "wonderful" C. Their syntax remind me of cryptographic methods to record the user can not understand where the programmer made a bull.
        Thus, for many years I remained at VB 6.0. Personally I use it to automate simple work to support my passion for photographing everything around him. There are many combines, which it can do better but do not do it as I want - in my way. And they are so great because everything is in them. In addition, I am not sure as to how much data about what I'm doing is leaking via the Internet. The old Visual Basic does not know how much power will the Web.
        For a private member such language, very simple with powerful capabilities is the perfect tool.

        I support the return of Visual Basic - may be version 6.1 with small upgrades to software developers who work on the 64-bitowcach also had the pleasure of nice programming in this environment.

        Roman Jezierski. Poland.

        Sorry for text in Polish, but my knowledge of the language of Shakespeare is too lame to express what I think.

      • DebugErrDebugErr commented  ·   ·  Flag as inappropriate

        Half a year later, basic butthurt's still whining in the comments.

        "Meanwhile, making up new unrealistic and stupid facts about VB6 continues"

      • dotNetterdotNetter commented  ·   ·  Flag as inappropriate

        Microsoft's cross-platform strategy is rendering Windows Phone irrelevant according to Lenovo

        Lenovo/Motorola say...
        "Unfortunately, Microsoft’s recent and necessary steps have obviated any need for ordinary users to even think about a Windows phone purchase"

      • Anonymous commented  ·   ·  Flag as inappropriate

        I know why they are not releasing a new version of VB6. They are AFRAID OF ITS' ANOTHER SUCCESS! If they had planned to release a new version it would be only for legacy support, but as they are decided not to do that it clearly shows the thing that I said above!

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        >> Another is that you may not be believed.

        It is crazy easy to identify trolls and troll accounts.

        I have yet to go into an COBOL, C, Oracle, .Net, Python or any other Professional forum and bash the users for using it. Professionals dont do that to each other. Ever!

        Think about it. You are bashing people for how they need to make a livelihood. Feed their families. Only trolls would do this. I have to agree that those that do this have psychological problems.

      • dotNetterdotNetter commented  ·   ·  Flag as inappropriate

        Apple have reported profits of $10.7 billion during the 3 months ending June, a 38% increase from a year ago.
        Sales of the iPhone increased by 35%, with sales of 47.5 million phones in the quarter.
        iPad sales fell by 18%, with just under 11 million units sold in the quarter.

      • dotNetterdotNetter commented  ·   ·  Flag as inappropriate

        Microsoft have reported losses of $3.2 billion during the 3 months ending June, it's largest quarterly loss ever.
        Analysts pointed to the weakness of the PC market and Microsoft's struggles in the phone market, together with some weakness in Office and Windows.
        A new release of Windows normally leads to a boost in sales, but as Windows 10 will be a free upgrade there will be little impact this year.
        Losses relating to the Nokia acquisition totaled $8.4 billion.
        Azure, Xbox games and Surface showed growth.

      • Alan HughesAlan Hughes commented  ·   ·  Flag as inappropriate

        One of the problems with trolling is that you may be falsely accused.
        Another is that you may not be believed.

      • HManHMan commented  ·   ·  Flag as inappropriate

        @Xavier

        "You put the question under Anonymous and after you respond."

        Hmm no, I did not. There is no conspiracy here my dear paranoiac friend, I have only ever posted any message whatsoever as myself, HMan. Period.

        "Who is the pathe_ticTroll ??"

        It's still you, don't panic...

      • EricEric commented  ·   ·  Flag as inappropriate

        Microsoft COO Kevin Turner has confirmed that Windows 10 will be the last major version of Windows. There won't be a Windows 11 or Windows 12, instead Windows 10 will be continually improved.

      • XavierXavier commented  ·   ·  Flag as inappropriate

        @HMan

        You put the question under Anonymous and after you respond. Who is the pathe_ticTroll ??

        .NET is dead, get over it !

        MS bring back VB6 !

      ← Previous 1 3 4 5 229 230

      Feedback and Knowledge Base