I suggest you ...

11,164 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

    4271 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...
      • ShaggyShaggy commented  ·   ·  Flag as inappropriate

        The 7 may be a bit constrained. The 8 gives you a bit more room at not much more cost.

        The real killer on those, as far as I'm concerned, is that they skimped on the memory. Memory is cheap and slim, so I don't see the point in having so little.

      • ShaggyShaggy commented  ·   ·  Flag as inappropriate

        It's not JUST the surface, but that is an excellent piece of hardware. I caried a Surface 2 Pro on a thousand mile bike ride (with an external battery and solar charger) so that I could work on a program in the afternoons. Personally, I believe that having a full Windows system in a tablet format is the likely future. Tablets are a size and weight that people find convenient, but who really wants multiple devices if one could do it all?

        There are others coming out that could also fill that roll, though the Surface is an excellent candidate. You might also look at the HP Stream, in one of its many iterations.

      • Sten2005 - vote for VB6 programmingSten2005 - vote for VB6 programming commented  ·   ·  Flag as inappropriate

        @axisdj

        The Surface 3 does look good. And with an Intel Atom processor it will run full Windows. At last we can compete with iPads - and VB6 (apps and the IDE) should run fine.
        Windows 10 is due in the summer and will make it even better.

        A reasonable price for a leading brand too.

        PS I see you aren't anonymous anymore :)

      • axisdjaxisdj commented  ·   ·  Flag as inappropriate

        As a community we (VB6 devs) have been fighting for Microsoft to bring back full support for VB6. I realized this morning that there is a MUCH better way to get MS to bring back support. We need to release Products/Apps/Freeware to the market that people use. With the new Surface3 tablets we have a perfect opportunity to release apps people will use.

        So, if we want to save VB6, build apps people will use on Surface3 and other Windows Tablets. Then MS will have no choice but to continue support.

      • Sten2005 - vote for VB6 programmingSten2005 - vote for VB6 programming commented  ·   ·  Flag as inappropriate

        @Edward

        "Their business model\charter must be committed to not requiring a complete code rewrite when they evolve their product."

        Even Microsoft agree with you.
        Paul Yuknewicz says "I definitely hear your point that change needs to be gradual & incremental. It isn't cost effective to keep rewriting code to get back to functional equivalence. "

        Unfortunately only Microsoft's words agree, not their deeds.

      • Anonymous commented  ·   ·  Flag as inappropriate

        @Sten

        "You don't need to use your real name, but using a unique name avoids confusion."

        Or use different names and IPs, like Marius and you have been doing for a long time?? This does NOT confuse according to you....right?

      • FramatoFramato commented  ·   ·  Flag as inappropriate

        You have not understood anything !!

        Microsoft has no intention to develop a tool for programming of desktop-oriented ...
        His intention is to bring everything in line, on the web, on the cloud ..... just so they can have the security of supply of Its useless services, and have total control of the software and customers, as well as Google and Apple are doing.
        They are adept at creating false needs and solutions to the needs absurd and useless which only bring other problems ... you understand that the only way they can survive and grow.

        Switch to the true open-source, and stop being like a flock of sheep following the shepherd.

      • EdwardEdward commented  ·   ·  Flag as inappropriate

        This experienced has taught me that:
        1. There has to be an open dialog between the development product decision makers you invest in and
        2. Their business model\charter must be committed to not requiring a complete code rewrite when they evolve their product.

        In this case we cannot speak with the business entity reps (other than requests which get denied without any explanation). Their long range goals include having to do complete code rewrites at the expense of the developer and clients.

        Good bye.

      • Sten2005 - vote for VB6 programmingSten2005 - vote for VB6 programming commented  ·   ·  Flag as inappropriate

        I would like to again repeat my request that people stop using the name 'Anonymous' - it is easy enough to set up another name (under Settings, top right). You don't need to use your real name, but using a unique name avoids confusion.

        I again request that posters stop spamming here, that the childish insults stop and that the repeated copy-and-pasting of barely relevant quotes should stop. If you feel the need to bring a quote to our attention, do so by all means - but don't keep repeating it over and over again.

        I have asked this on several occasions, perhaps this time posters will take notice.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Michael

        Please stop playing the victim and face the reality. By the rules of the uservoice forums, you can NOT make the same request over and over again. Be honest to yourself, the request that Mary placed was in fact requesting to bring back VB6 although indirectly. Thus. it was rightfully removed by Microsoft for that reason. Also I don't think that your messages are considered powerful by MS, as there were lots of hypocrisy in your other rants in this forum.

      • MichaelMichael commented  ·   ·  Flag as inappropriate

        I wonder how many developers would have started down the Visual Basic path knowing how they would ultimately be treated? Mary has two very powerful words for Microsoft that I'm going to use here too. These two words may be the most powerful message to Microsoft we can deliver.

        Good bye.

      • Anonymous commented  ·   ·  Flag as inappropriate

        @Sten2005

        "It doesn't seem like Microsoft is concerned about spam, just look at all the childish and repeated copy-and-paste spam postings we see flooding this thread everyday"

        Well, you were honored to be Marius Orion, the childish psychopath spamming here everyday and even putting obscene ascii pictures all over. Remember what you've said? "And I too am honored to be considered to be you Marius."
        So the logical deduction is that you are not disturbed by top spammer Marius at all, as you are honored to be like him. Hmmm, funny...but rather pathetic...You see Marius did not help your cause and actually hindered it. It is a well known fact that you have been banned on other forums before, because of this attitude of spamming, falsely accusations,arrogance, aggressive behavior,personal attacks etc. Seems like Microsoft also is fed up with this game you and similar characters have been playing here for a while. Why don't you guys just stop this childish game, grow up and do something useful with your lives? May be this slap of Microsoft on the face will teach you something and correct your attitudes. But I highly doubt it......

        "And I too am honored to be considered to be you Marius."

      • Sten2005 - vote for VB6 programmingSten2005 - vote for VB6 programming commented  ·   ·  Flag as inappropriate

        Microsoft have taken the view that Mary's call to merge VB6 programming into Office or Windows is the same as this thread requesting an updated VB6.

        It seems strange that Microsoft are unable to tell the difference between the two suggestions.

        Microsoft have made it clear that they have no regard for VB6 developers (or customers as Microsoft should see us).
        Clearly they can have no expectation that VB6 developers will ever move to any other Microsoft language. Who would when they can see Microsoft's attitude ?

        Windows 10 is due out this summer, it will be interesting to see what Microsoft announce about VB6 then. It is expected that they will extend VB6 support beyond the current 2024 end date.

      • MaryMary commented  ·   ·  Flag as inappropriate

        I'd like to sincerely thank Microsoft for providing this forum to allow us to make requests. Thank you also for creating Visual Basic 6. It really was and is the best software of its kind. While it did not have all the OOP bells and whistles some clamored for it did allow us to create and maintain solutions that got us home to our families without working all night.

        Good bye.

      ← Previous 1 3 4 5 213 214

      Feedback and Knowledge Base