I suggest you ...

11,213 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)  ·   · 
    Luis Fernando Echeverri LozanoLuis Fernando Echeverri Lozano shared a merged idea: VB6 Honoris Causa  ·   · 
    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

    5060 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...
      • VB6userVB6user commented  ·   ·  Flag as inappropriate

        @Lofaday

        >>What I don't want to keep secret for anyone with enough smarts is that MS will chew you quicker than you can say "dishonorable".

        So true :(

        But at least they have been forced to concede that " the core Visual Basic 6.0 runtime will be supported for the full lifetime of supported Windows versions" :)

      • VB6userVB6user commented  ·   ·  Flag as inappropriate

        @Anonymous

        Good find. :)

        That link says...

        Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1, Windows Server 2012, and Windows 10
        Update: August 2015

        Executive Summary

        The Visual Basic team is committed to “It Just Works” compatibility for Visual Basic 6.0 applications on the following supported Windows operating systems: Windows Vista, Windows Server 2008 including R2, Windows 7, Windows 8 and Windows 8.1, Windows Server 2012 including R2, and Windows 10.

        The Visual Basic team’s goal is that Visual Basic 6.0 applications continue to run on supported Windows versions. As detailed in this document, the core Visual Basic 6.0 runtime will be supported for the full lifetime of supported Windows versions, which is five years of mainstream support followed by five years of extended support ( http://support.microsoft.com/gp/lifepolicy).

        Those posting here that VB6 is no longer supported are just wrong.

      • Sten2005 - Microsoft support VB6 programming on Windows 10Sten2005 - Microsoft support VB6 programming on Windows 10 commented  ·   ·  Flag as inappropriate

        The utility to install the VB6 programming IDE in Windows 7,8 and 10 has now had over 60,000 downloads.

        http://nuke.vbcorner.net/Articles/VB60/VisualStudio6Installer/tabid/93/language/en-US/Default.aspx

        And there is a YouTube video at https://www.youtube.com/watch?v=1tkTb6AYlAg

        Microsoft support VB6 on Windows 10 until at least October 2025.

      • HManHMan commented  ·   ·  Flag as inappropriate

        "There's a second point about what you are really getting with different frameworks"

        It's pretty simple really, each framework is an iteration on the last one. If you use 4.5.2 or 4.6, you get everything that was ever included in .NET before it. .NET 3.5 contained 2.0, and 3.0. 4.5 contained 2.0, 3.0, 3.5, 4.0, etc... The reason they are retiring the old ones is simply to make deployment simpler. The last couple of versions they introduced fixes to base classes introduced in previous versions, so at the moment there could be rare deployment issues if an application was developed on 4.5 but the client machine has 4.5.1 installed.

        For the programmer, making the change is as simple as changing a project setting and recompiling.

      • ShaggyShaggy commented  ·   ·  Flag as inappropriate

        @Anonymous: Well, that's not exactly correct for a couple reasons. MS is saying that the others are out of support and they recommend updating to continue to get support. VB6 has been out of support for about a decade, now, but that doesn't mean it won't run.

        There's a second point about what you are really getting with different frameworks, but I don't care enough about it to learn it in sufficient detail to talk about it. Basically, it may not matter whether the framework is targeted, you may be using it anyways.

      • Lofaday - mail me on VB6 at QSL dot EULofaday - mail me on VB6 at QSL dot EU commented  ·   ·  Flag as inappropriate

        @Anonymous re https://www.linkedin.com/pulse/net-frameworks-being-retired-next-six-months-martin-allen

        Wow indeed! Meanwhile, for those that might remember me as an occasional commentator, I am now making loads of money out of VB6 again.. As a consultant, I knock up a concept app in minutes flat and ask some kids with drive in movie screen foreheads (HMan?) to "duplicate that" with whatever the customer happens to want (C#, VB.net, java, who gives a fig). It takes them weeks to do what I did in minutes. I don't want VB6 back, I want to keep it a secret.

        What I don't want to keep secret for anyone with enough smarts is that MS will chew you quicker than you can say "dishonorable".

      • Grant SwingerGrant Swinger commented  ·   ·  Flag as inappropriate

        @MichaelE, Since PowerShell can access the .NET classes you can use Windows Forms to build a GUI. This TechNet article is a good description:

        https://technet.microsoft.com/en-us/library/ff730941.aspx

        Of course, you're doing this by hand just like building a GUI in an HTA. If you do a lot of this then investing in a product like PowerShell Studio 2015 may be worth it. I don't do enough PowerShell GUI work to justify buying this but I know admins who swear it was worth every penny (about $390) and then some.

        Or you can jump into XAML and use Visual Studio to build an IDE. This blog has a series on it:

        http://foxdeploy.com/2015/04/10/part-i-creating-powershell-guis-in-minutes-using-visual-studio-a-new-hope/

        On the other subject, VB6 fans invading .NET topics to advocate for the return of their favorite development tool used to be common. It pretty much ended after MS brought down the DECLINED hammer on every suggestion they didn't outright delete.

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        @Grant I am pretty versed with Powershell but have not been able to use it for any scripts that needed a practical - somewhat robust GUI (other than purchasing a 3rd party product). Have you created any significant GUI's using Powershell? If so please share where this info can be found.

        Thanks!

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        @Grant I am not looking to replace my VB6 apps with HTAs. I have done most of that with Python. Your words and those from Microsoft support do not quite align. In some instances I needed a quick and simple GUI for some small apps (database interfaces).

        I did not want to invest in any MS technology that was not going to be around. MS said it will be around for quite a while. They will be including IE on their Windows OS's for some time to come though Edge is now their preferred Browser.

        As a side by product I objectively became aware that the manner I implemented it was in fact using 64bit VBscript 64-bit ODBC (etc.) thus I thought I'd share it here a VB6 oriented request.

        Respectfully, I would say to anyone extremely pro .Net to focus there and not be too concerned with the "noise" us remaining VB6 appreciators make. I noticed the VB6 folks dont invade .Net posts and counter every post with everything they are doing wrong and that they should be using Java or VB6 etc. (not that you @Grant do this - but some here do).

        I will post my findings shortly on what I did and how. In this way anyone that wants to can duplicate it if they choose to. Correspondingly, anything I come across that is useful to .Net I will post in appropriate .Net thread.

      • Grant SwingerGrant Swinger commented  ·   ·  Flag as inappropriate

        HTAs were a great idea when VB6 was a great idea - back in 1999. A lot has changed since then and HTAs along with VBScript are old and busted. They've been replaced by PowerShell and .NET.

        You do not get HTML5 support in an HTA. You can't use the hardware accelerated Canvas for one thing And they're not supported past IE9:

        https://connect.microsoft.com/IE/feedback/details/78505/hta-application-tag-does-not-work-in-ie10

        Seriously, you are grasping at straws here. If you need a 64-bit application why not use a modern programming language?

      • MichaelEMichaelE commented  ·   ·  Flag as inappropriate

        @HMan HTAs are not designed to create .Net applications. To me they are a useful tool. It is amazing how far they can be extended.

        Maybe you found different but I have been finding interfaces created with HTML5\CSS are state of the art and not bound to any IDE version controls implementation. Sorry your HTA interfaces have been less than desired. There are some good sites on HTML5 out there. I'd say start with w3chools.

        You sound like you have been creating HTAs for a long time. I bet I could learn a lot from you there too. I'm going to be posting some some the apps I created shortly and the results of my conversations with MS on it. We could collaborate.

        @Hman can you post any examples of HTAs that you have created?

      • HManHMan commented  ·   ·  Flag as inappropriate

        @MichaelE

        Sure, you can use HTA's, but they are not VB. It's HTML + VBScript (or JavaScript). Second, running it with 64-bits mshta.exe means that you will not be able to load ANY 32-bits COM components.

        "You now have applications in VB that looks better than any .Net"

        No. Just no.

        "you only need to write to one Browser, there are no http security issues as its not using http"

        Correct, as it is only for LOCAL applications, and will always be rendered in MSIE.

        "its response is fast"

        That mostly depends on the contents. That's like saying "Hondas are fast!".

        "no run-time is required to be installed"

        And nothing included either!

        HTA's are just a GUI extension to the Windows Scripting Host. They have been around for as long as .VBS scripts. It's fine if you only need to script something quick and have a GUI and only have notepad on hand. You won't get far if you try to develop a full application in it.

      ← Previous 1 3 4 5 252 253

      Feedback and Knowledge Base