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

    4507 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...
      • Microsoft, update or open source VB6 programmingMicrosoft, update or open source VB6 programming commented  ·   ·  Flag as inappropriate

        @MichaelE

        Yes, we have reached 4500 comments here - plus more on other threads. All those posting have helped put pressure on Microsoft to ensure that VB6 continues.

        Thanks to everyone - for or against VB6 - who have ensured that VB6 programming continues.

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        I'd just like to pass on that I am grateful to Microsoft for its continued support of VB6. Though it is certainly not my core tool at this point it has its place just as batch files, PowerShell scripts and other tools.

        I'd also like to thank @HMan and the trolling accounts here. By inflaming part of the VB6 community you may have contributed to Microsoft's including the VB6 runtime in Windows 10.

        Thanks!

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        >> @HMan would Microsoft continue support for a product that did not have a significant number of users?

        You did not answer the question. You put your spin on it and took it out of context.

        Why would Microsoft put any resources into ensuring the VB6 runtime is supported\installed\works\<label42> if there were not significant number of users?

        "Works" means it works as opposed to "not working". They guarantee that "it works". Do you guarantee the software you write works?

        Why dont they also include the run-time for VB 3,4? Why dont they include the run-time for GW-Basic? How about Access 1.x and 2.x?

        Seems they include the VB6 run-time because there are a significant number of users to Microsoft to warrant their action.

        @Hman if you have any info from Microsoft to the contrary please let us know.

      • HManHMan commented  ·   ·  Flag as inappropriate

        "The last article clearly indicated 100k Navy users (of course none of those are using the VB6 run-time)."

        The last article indicated 100K Navy SYSTEMS still using Windows XP... and they will all be updated by next year. Nothing (at all) about VB6 in there. Of course you can choose to read whatever you want into it, just like you did with your "hundreds of thousands" VB6 programmers...

        "@HMan would Microsoft continue support for a product that did not have a significant number of users?"

        Except they DON'T support it, it just works as is. Considering they had nothing to do for this to happen, it's not surprising. If it ever stops working, you're STILL on your own...

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        @HMan would Microsoft continue support for a product that did not have a significant number of users?

      • Green TeaGreen Tea commented  ·   ·  Flag as inappropriate

        HMan thinks this is sarcasm by Microsoft...

        "Windows is committed to compatibility. The Windows compatibility team has been looking at user telemetry and reacting to feedback from Windows Insiders to ensure that existing apps work well with Windows 10. Windows 10 is designed to run Windows 8.1 and Windows Phone 8.1 software programs. And yes, everyone’s favorite VB6 Runtime will continue to work, too. In the near future, the compat team will go more in-depth on this topic on 'Blogging Windows'."

        http://blogs.windows.com/buildingapps/2015/06/22/getting-ready-for-windows-10-sdks-compatibility-bridges/

        I'm not sure that Microsoft are renowned for their use of sarcasm, especially about their own products.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        Ah so @Hman hides behind a fake name calling foul that others make up fake stats.

        The last article clearly indicated 100k Navy users (of course none of those are using the VB6 run-time). Countless links are posted here of how many times the VB6 run-time is downloaded. One can build a case for or against anything though.

        Lets let Microsoft have the final words. They are not hiding or skewing anything:

        "Windows 10 is designed to run Windows 8.1 and Windows Phone 8.1 software programs. And yes, everyone’s favorite VB6 Runtime will continue to work, too."

        http://blogs.windows.com/buildingapps/2015/06/22/getting-ready-for-windows-10-sdks-compatibility-bridges/

        "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." -Paul Yuknewicz, Group Program Manager, Microsoft Visual Studio Cloud Tools

        @Hman you had your day in the sun when an obscure crowd funding site did not raise money. Sorry VB6 is here to stay. You dont have to like COBOL or C either but they will be around for a while too.

      • MeganMegan commented  ·   ·  Flag as inappropriate

        Oh look that gazelle saw the shadow of a grizzly bear in the river bed! VB6 will live forever!

      • HManHMan commented  ·   ·  Flag as inappropriate

        @dotNetter

        Oops you are right, Anonymous said that, you just happened to be the one to respond. Apologies. "You" in that case referred to Anonymous.

      • dotNetterdotNetter commented  ·   ·  Flag as inappropriate

        "You guys would get a lot more credit if you didn't behave like children making up stuff as you go to make yourself look good."

        Looks like it is you who is behaving "like children making up stuff as you go to make yourself look good.

      • dotNetterdotNetter commented  ·   ·  Flag as inappropriate

        "You however stated with certainty that there are hundreds of thousand of you. You didn't suggest or even imply, you stated categorically."

        Show me where I stated that.

      • HManHMan commented  ·   ·  Flag as inappropriate

        @dotNetter

        "Is that a statistic you have made up ? Show us some sources."

        Nope, just what I think, as the sentence structure clearly indicates. I didn't say "there are less than 20 thousand" I said "I (as in me) highly doubt there is even 20 thousand". I think the syntax was pretty clear.

        You however stated with certainty that there are hundreds of thousand of you. You didn't suggest or even imply, you stated categorically. So you do need to show sources. But you have none, because you made up this statistic.

        You guys would get a lot more credit if you didn't behave like children making up stuff as you go to make yourself look good.

      • dotNetterdotNetter commented  ·   ·  Flag as inappropriate

        "Pretty sure this was sarcasm in their original post."

        Pretty sure that is your wishful thinking.

      ← Previous 1 3 4 5 225 226

      Feedback and Knowledge Base