I suggest you ...

12,075 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Eugene shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    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
      Signed in as (Sign out)
      • SuperDre commented  ·   ·  Flag as inappropriate

        @mjohn: FYI, C# isn't a closed-source language.... and as I see what's "up" I'm even more depressed, javascript and html5 aren't great technologies and therefore I'm not glad they are "up", let's waste even more precious resources on yet more interpreted ****.. We already need much more powerfull computers just to run the new versions of the same applications we already ran a decade ago, with only a bit of better options..

        And for people who are still thinking silverlight will continue... Nope it won't, Silverlight 5 was the last version that's gonna come out, MS has replaced it with HTML5/Javascript..

      • VB6 Programming commented  ·   ·  Flag as inappropriate

        That is exactly it. As a minimum we need to know that VB6 applications will continue working with each new Windows version. Preferably that should apply to the IDE as well as any applications.

        A new version could have new or improved features (64 bit support, Try..Catch, runtime for WinRT - I'm sure we could all put forward our favourite suggestions) but really that is just a nicety. The important point is to be sure that legacy applications will continue to run.

        We don't want to be in a position of having to tell our users not to upgrade their Windows because it does not/may not support our applications.

      • Madrianr commented  ·   ·  Flag as inappropriate

        same here Leonardo Azpurua - we have a large CRM VB6 application

        and we have also a Lightswitch app out but many problems - slow sluggish interface, lot of bugs and no response from MS about this and the future of the silverlight client...

        I don't know whats going on at M$ but thats not acceptable!!

      • Anonymous commented  ·   ·  Flag as inappropriate

        No. What I want is to be able to continue improving my 500+KLOC system written in VB6 without having to worry every time that MS announces a new Windows Versión for which VB6 support is expressely announced to be lacking. Ok, they have to put it back every time, but they will eventually fail big (I mean, someone who is so stupid as to kill VB6 may do any absurdity at any moment) and that's game over for me.
        I saw a couple of videos about LightSwitch, and it may have some of the simplicity of VB6 form design. I don't know how good it is to handle large projects, to write libraries. to implement user-controls that act as visual representations of the enterprise objects. But no matter how good it is, it won't take that huge amount of code of mine and execute it cleanly without any change.
        VB Net is fine, LightSwitch is fine, PHP with JavaScript and HTML/CSS are fine, C# is fine, Java is fine, every **** language is fine.
        I don't care about languages, I don't worry about languages, I just don't want my code to sink into obsolescence because some stupid salesman has a bright idea, or an evil executive devised an strategic plan.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I think most are missing the point for the passion. The point is we want a simple, easy to use, understand and implement system for quick deployment of business/customer needs! Call it whatever you want or write it in whatever language you want, but the average problem solver should not have to have a degree in a particular language that changes faster than the tax code! Remember the old adage - KISS is best. For those .net folks that stands for Keep It Simple S*&^head!!!!!

      • aa commented  ·   ·  Flag as inappropriate

        Bring back Visual Basic
        There is a real issue of how to support legacy VB6 applications. Upgrading to VB.net isn't possible for large applications. Yet Microsoft ignores this. Either bring back classic VB6 or open source it.

      • Dean commented  ·   ·  Flag as inappropriate

        The Cloud = putting your data on someone elses computer so they can **** it.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Besides fancy people doing fancy things with fancy devices, there is people who spend several hours a day transcribing data. Even after putting all the fancy little gadgets to fancily do most of the work, there are lots of tasks that are best performed using a full size keyboard to type on a large screen. And once you get used to a mouse, it is as good to select and click things as a finger on a touch monitor. With a mouse you may replicate most of the gestures you do with your fingers on a touch screen. Besides, allowing the pointer to rest at some place is also a gesture, which you can't replicate on a touch only device.
        There are classes to consume SOAP services from VB6, you may also use the internet transfer control to gain access to sources of information not as structured as SOAP Services, but nevertheless available. You may also POST information to web servers, open connection across dedicated lines, VPNs or the plain internet.
        So what are the dreadful limitations of classic VB?
        What led someone at MS to dismiss VB6 is probably one of the most stupid, absurd and senseless examples of prejudice in the history of mankind.
        "The cloud" is just a heap of information piled up somewhere. At the end, "the cloud" boils down to one end point that answers to requests that comply with a certain protocol: you send bytes, wait for a proper reply, receive bytes and process them. That could as well be done with Fortran or COBOL. That's what computers have always been about, more or less since UNIVAC days.
        What is really new is hype dominating common sense and salesmen conducting technicians.

      • eric au commented  ·   ·  Flag as inappropriate

        Agree with Leonardo. Internet has been around for 20 years and .Net has been around for 10 years, and today people are still talking about the cloud is the future. Yes it's true, and it will still be the future in the future.

        We are asking for a successor of VB6 because VB6 was the world's most popular development tool at the time MS decided to kill it. We need a tool to get thing done easily, rapidly and done well. It will be a success if MS allows VB6 to evolve in the right track.

      • Madrianr commented  ·   ·  Flag as inappropriate

        @Leonardo Azpurua: we are in the same situation - everybody takes about html5 but do not understand that there a also the need for apps with interop (office integration, reporting, drag & drop, keyboard navigation)...

        VS 2012 is slow and not a RAD Tool - we small companies need a tool to build apps very quickly - Lightswitch was a good idea but MS has killed the silverlight version which was good for building LOB applications...


      • ssjx commented  ·   ·  Flag as inappropriate

        Win7 phone break wince, so win7 is dead.
        Win8 phone break win7, so win8 phone will be dead too.
        Win8 rt break win32 api, so Win8 rt must be dead.
        Today, New lanauge has no change to alive, specifically close-source language has no change to alive.If has no mono, .net and c# will die quickly too.
        Today, c/c++,objc,javascript, html, these old langages are the master of the computer.
        It is not c#, is not the .net framework, not the closed-source language.
        So c# and .net has no future if has no mono.
        Microsoft has no future is it break compatibility again and again.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Who cares about the future?
        Today, I have about 2000 customers using a system written with VB6. Some of them have needed web support for their operations, and I have provided it. Others have requested to go mobile, and I have provided it. Of course, not all has been done with VB6, but the core system is. And it is a fairly large system.
        Most of Office Automation is done through COM, which may not be useful in all this new world, but which is still much used for component and programs interoperation within the local computer.
        Interop is still needed, and will always be. And breaking COM would mean breaking LOTS of computers.
        The future is fine, but they can't break the present and get away with it.
        They should know!

      • Anonymous commented  ·   ·  Flag as inappropriate

        i do not understand you .... I too loved vb6 , and vc++ 6 too ....but get over , COM is history and has to go away , future is xaml,cloud,services,wcf not vb6

      • Dean commented  ·   ·  Flag as inappropriate

        Uncle Fester's put the Start button back!!

        Whatever next?

        VB6 re-released and bundled with free NSA backdoor API!!!

      Feedback and Knowledge Base