I suggest you ...

10,807 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…)
    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    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  ·   · 
    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  ·   · 
    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


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      • Ready for youReady for you commented  ·   ·  Flag as inappropriate

        "I think that .NET is going to be with us for a long time" -possibly, but, with that strategy Microsoft starts to become an insignificant player in future. Remember, VB6 led Microsoft in to the top immediately. On the other hand VB .NET strategy did not convinced anyone even after 16 years ... but VB6 still is/will be !

      • MichaelMichael commented  ·   ·  Flag as inappropriate

        @HMan thanks for your post.

        >> but hey hard to ask from him what your own anonymous guys can't deliver...

        If we want to raise the bar there is no "your own anonymous guys". Just us. Just all developers. ;-)

        Something for us all to work toward. Small steps.

      • HManHMan commented  ·   ·  Flag as inappropriate


        It really has no bearing in the end, what he posted was comments from other people, named. Granted, sources would be nice, but hey hard to ask from him what your own anonymous guys can't deliver...

      • MichaelMichael commented  ·   ·  Flag as inappropriate


        1. Is it possible for you to not hide behind a @Anonymous so we can see your credentials?

        2. Do you have a professional website or linkedin.com page where we can see the kind of code you write and your resume?

        3. If those quoted posts are real please post the links.

        Lets raise the bar.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Jeff I.

        Freelance Software Developer/Consultant/Certified oDesk Contractor

        Let's look at it this way. Ultimately, everything has to run on a machine. Open source? That's a paradigm not a programming technology. As far as .NET goes, the CLR is the heart of the matter. As we move into the future I think this paradigm is going to be an absolute necessity. Whatever the future holds as far as programming techs go, I think they're going to get higher level requiring that there be some intermediate compilation from a high level programming tech to some intermediate state and ultimately down to machine language so it can be executed. We already have that - .NET. That's what it's all about. So yes - I think that .NET is going to be with us for a long time. Any successor will be designed according to the .NET paradigm by necessity. I'm not the biggest Microsoft fan, but I do think that the .NET paradigm is not only the present but also the future.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Gavin S.

        Founder / CTO at Solid Cloud, LLC

        Microsoft continues to invest in Visual Studio and Azure. The tool support for developing software continues to get better. To me using Visual Studio vs other tools there is no comparison. This is much like asking a graphics designer to create graphics in Paint vs Photoshop. As Software Development continues to become more like Engineering, these tools will become more and more important. I'm sure PHP / javascript will be the same today as they will be in 20 years, but I'm pretty confident we'll be another 2 levels of abstraction higher on the MS toolset. In the end, there is no comparison, and no better toolset for developing software.

      • Anonymous commented  ·   ·  Flag as inappropriate

        yasien A.

        Senior Software Developer at ADVAC Systems Ltd.

        Microsoft professionally knows the game .Net and most of Microsoft products will always be dominant . Because i think recently .net creator trying to combine the best practices and technologies and ideas built in other platform in one place called .net. and of course most of the developers like this approach (to find everything in one environment)

      • MichaelMichael commented  ·   ·  Flag as inappropriate

        [VB6 Facts vs. Fiction]

        Though I added dozens of source links the page is not what I would consider finished. I am putting it out again for RFC.


        Fellow developers my intentions in posting this are not to lobby for VB6 forever. Just to move the community to a more facts based understanding of VB6.

        .Net folks if you TRULY want all the VB6 folks to migrate to .Net (when they can) then dont accuse them of being stupid, lazy, out-of-touch with modern programming or anything of the kind. The facts simply dont support this.

        Some are saying that blatant negative posts are originating from Paul Yuknewicz and\or a highly polarized agenda based kill everything not .Net group. I dont know if that is true but again those kind of posts just polarizes people deeper. You get things off your chest but dont change anything.

        We have to figure at this point that any @Anonymous poster that blast .Net or VB6 have no credibility - and of course any legitimate sources.

        Why dont we raise the bar? Some will be using COBOL in 100 years. Let them be already. Same with people using VB6. We cannot know all the reasons they stay with VB6. In most cases it certainly is NOT because they are lazy or stupid.


        Bravo VB6 and its heyday. Cheers to .Net.

      • Ready for youReady for you commented  ·   ·  Flag as inappropriate

        Microsoft "evangelists" present the news stuffs as good !: a comment by Michelle

        I guess should be the time to seriously think about to abandon Microsoft and their moods. I would remember that EACH SINGLE time they release a new technology, they present and SELL IT as the absolute and definitive good solution for ever. While, in the meantime, they constantly show all the weak point of the past technology like if was made from somebody else!
        I've partecipated to hundreds of workshop from Microsoft and their "evangelist" and ALWAYS they present the news stuffs as good, past stuffs with absolutely BAD even if THEY MADE IT. This happened with RDO and then, after a little while ADO was suddendly the new way to god... Also with IIS happened the same. And now it happen with the SDKs...For who is taking the time to read this post, please consider that from .Net 1.0 to .Net 4, ALWAYS a "porting" was needed! Even if you used .Net... but with the new wrong version! At Microsoft seems they do not care AT ALL about developers.
        They seems not to understand that all the above "moods" COST MONEY other than time! Bigger the company bigger the costs. Not all the software company around the world have the resources Microsoft have! I hope those are only "moods", otherwise that means at Microsoft they do not know what they are doing! At moment, seems that developers are binded with their operating system and if you want to produce YOUR software, you MUST agree with their politics. Take it or leave it. If you don't agree, you just loose all what you did till that moment! I perfectly understand that the world need to be innovated, but then two considerations came to my mind:

      • Ready for youReady for you commented  ·   ·  Flag as inappropriate

        1) I wish to be FREE to decide if I NEED to innovate myself or forced to do it, paying otherwise the penalty to loose my customers or job.
        2) If innovation is in terms of software "theology", structure, OOP etc. and the porting from "the past old bad stuffs and habits" is the "new" .Net way of light, please consider that JAVA it's like is .Net NOW, but just years and years ago! So if we want to talk about innovation, then it is Microsoft that is LATE about 10 years, not WE as developers. WE JUST BELIEVED TO THEIR ABILITY to provide a working environment to build software. And Visual Basic 6 IT IS EXACTLY THAT. So, if we are talking about "innovation" seems then that all the developers that trusted on Microsoft's solutions have really used very OLD stuffs, not competitive since the beginning. So, how many of you still believe to continue trusting in Microsoft?
        How long this "new and good" .Net technology will remain the same, until the new "porting", in the name of the "innovation"? We have to still trust about the forecast for the support of this .Net product? What about the mandatory switching to Windows 8 if you want to INVEST into the new latest versione of .Net? How many of your customers will feel comfortable to mandatory switch to Win8 only because you started to use the latest .Net framework? Personally, because of the amount of the products and related code I've done in these years I CANNOT AFFORD to "port" it to .Net. Too much complicated. Dot Net is good for "complex" stuffs to do with VB6, but incredibly slow and difficult for basic everydays stuffs. Not to mention the protection of the intellectual property, that with .Net it is simply impossible to really protect. Well.. there are "obfuscators"... good to stop just my grand mother...
        That said, if a new Linux Basic SDK appear on the market, I'll for sure reccomend it to ALL OF MY customers, suggesting to switch to Linux. Probably I'll do the switching for free then! Incredibly less cost, more performance, more stability, less problems system-wide. If a new "Linux Basic" that REALLY WORKS will be sold for Linux, I'll go to buy it. 100%. So, who is able to do a compiler, should take this opportunity that Microsoft left open! Whoever will make a Linux Basic, have a market of thousands and thousands of developers, READY TO GO. Those developer, like me, are simply tired to be kept by the neck from Microsoft. We do not switch to other systems simply because there are no good alternatives, or good economic alternatives.
        Well... if I'm FORCED to INVEST my time and MONEY somewhere else, there is JAVA, that prooved to be made from who have clear idea in mind about software industry and how to respect who kept the company grow. Do you think that Microsoft could sell so many licenses of Windows and Office, if there was not so many developers around the world?
        I respect what Mr. Paul Yuknewicz said. Technically speacking, his points are honestly good points, but economically speacking, and in the way Microsoft usually put decisions, it is totally unacceptable. Refactor VB6 is difficult?!!? This maybe means that doing the .Net was easier?
        We have no way to force Microsoft having a "GOOD SENSE OF PRACTICE" other than go away and leave them alone.
        So, this is a WORLDWIDE CALL to any developers that are able to make a SDK that have the same ability of VB6, but opened to all the suggestions made in this forum, actualize it, make it for mobile applications too, if possible and with the obvious constraints.
        BUT running onto a serious platform: LINUX.
        That one will be then a "porting" that could make some sense to do... and not blindly still follow the Microsoft "evangelists" (I'm not kidding. They call like that, by themself, at least here in Italy...).
        Kind regards.

      • refgrefg commented  ·   ·  Flag as inappropriate

        A message from Vorlon:

        I am an analyst and programmer, I know most programming languages and I am also a VB6 lover (and I say with great pride):
        Analyzing the text messages it seems that Hman and "that" Anonymous are one and the same. Hman may be Paul Yuknewicz ! yes, him.There is pathos in this for Paul, because he advocated .NET in 2001 from what I understand.
        If these comments against Visual Basic 6.0 appeared for several weeks, this means that all the struggle for VB6 comeback has a serious echo inside Microsoft. We see a lot censorship and VB6 ideas rejected on uservoice.com without explanation. Why do you think?! If you/we quit now, you/we are f o o l s.
        In all the negative posts you will see an increased frequency (a pattern) of words: "patheti.c", "delusiona.l", "period.", "Again,", "case closed.", "childish", "spamming", "VB6 is dead" or "switch from VB6 to .NET" and so on. These words enter in a single pattern, belonging to only one man! Folks, just a simple idea posted here has 11,000 votes and 3,100 comments, THAT IS HUGE and really annoying for .NOT preachers (based upon common words and the style of the messages, I counted four . NET preachers across the Internet).
        In order to discourage the VB6 community, they (Paul Yuknewicz and the orchestra) applied the same tactics in 2008. They employed about 3 or 4 people to negatively comment on the internet with regard to VB6, and it worked ! But Microsoft has other smart people who are pro VB6, which realize the importance and the size of the VB6 community.

      • Anonymous commented  ·   ·  Flag as inappropriate

        crazy nut ml (Marius Orion) like other vb6 nuts in here thinks that .NET is only winforms,wpf and silverlight. Shows those VB6sters have absolutely NO clue whatsoever in terms of what .NET is and will be. There are so much more that ensures .NET will be here to stay for a very long time. Have those guys (ml,Sten2005,winston etc.) heard about XAML, WCF,Reflection etc. etc. The .NET is NOT a User Interface for god sake! It is an extensive framework and those libraries will never disappear but will be used and developed further. Silverlight is a subset of WPF, so disappearance will not effect .NET framework. NetCore (with Net native) is a subset of NET Framework again. WPF is a philosophy to design UIs with business model separation in mind. MVVM is build-in and facilitated through XAML. These technologies will NOT disappear, but will be amalgamated possibly under some other name. In the future we probably will see a crossplatform targeting desktop/mobile utilizing all the core elements of NET framework. This is inevitable and from what we see this will happen within the next decade.
        In the meantime, VB6sters keep on dreaming of a comeback of VB6. I wonder how you will port your wonderful legacy applications to crossplatform multi device platforms in a decade from now....keep on waiting and dreaming...

      • HManHMan commented  ·   ·  Flag as inappropriate


        If you knew how to read, you would understand that .NET Core is a separate target than .NET Framework. The existing technologies will continue to evolve (as demonstrated in the upcoming .NET 4.6), and .NET core will evolve in parallel.

        You just don't have a clue what you are talking about. You can't even read a blog post WITH DIAGRAMS properly, so why don't you leave the real stuff to the grown ups?

      • mlml commented  ·   ·  Flag as inappropriate

        Understanding .NET 2015

        From the above blog, We should know, .net's future is .net core(asp.ne mvc6 and universal windows apps).

        The old .net technology(winform/wpf/silverlight/LightSwitch/asp.net winform...) will die slowly in next years, so don't waste time on these deading technologies.

        And because "universal windows apps" only for windows and is close-sourced, and after five years "universal windows apps" probably be killed by microsoft again, so don't waste time on "universal windows apps".

      • HManHMan commented  ·   ·  Flag as inappropriate

        Good old ml, always with his erudite grammar and so polite conversation...

      • mlml commented  ·   ·  Flag as inappropriate

        Today, a .net guy create a new uservoice: Kill VB language Foreva

        I think this guy want kill vb.net from .net. i have see some other uservoice ask for kill vb.net too.

        As i had said, Microsoft is very stupid to create both c# and vb.net language for .net. Remove vb.net from .net is the best choice, don't waste the human resource in vb.net.

        After .net core is open-source, every project about .net core in github is c#.

        Because as a .net dog(@HMan) has said, "vb.net is can be transfered to c# easily", so if this is true, then remove vb.net language will not make trouble, the vb.net guys can transfer to c# easily, need't rewrite.

        If someone really want rewrite a project use .net, don't use vb.net, use c#. don't use the old .net framework, use the new open-source .net core. dont' use .net for desktop software and big website, .net is only suitable for small enterprise and small business web project.

      • Anonymous commented  ·   ·  Flag as inappropriate


        Mr. Sten behaves generally like this. When you corner him with legitimate questions and facts, he pulls the conversation into you and me type polemics. He does not reply to the points that we make here everyday, as he knows that he doesn't have neither the ammunition nor the know-how to fight. He reminds me that poor fellow Winston in many ways. VB6sters must be drinking same cool aid.

      ← Previous 1 3 4 5 168 169

      Feedback and Knowledge Base