I suggest you ...

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)

The silent majority of VB6 users did not ask for changes that came with .NET

We request Microsoft brings back classic Visual Basic as COM development is back with Windows 8.

Reloaded from: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi

3,433 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…)
    VB6 FireVB6 Fire shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    RR shared a merged idea: Bring back Classic Visual Basic, an improved version of VB6 (reloaded from 7400 votes)  ·   · 

    1181 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...
      • Anonymous commented  ·   ·  Flag as inappropriate

        @Anonymous --Is there any developers here who have a courage to develop a reverse engineered version of vb6?

        ---reverse engineering is not an appropriate way to bring back vb6, at least MS's lawyers will prevent you. the only option is looking for a "behavior exact the same as vb6" compiler and runtime, currently, not available yet. but soon will be, I expect. So will you guys pay for a behavior-exact-the-same-as-vb6 IDE/compiler/runtime if it will charge you for a commercial license?

      • Anonymous commented  ·   ·  Flag as inappropriate

        Is there any developers here who have a courage to develop a reverse engineered version of vb6?

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

        @Ed, well said. We decided that long ago (drop Microsoft). Just finished manufacturing 150 devices based on computers running Linux. No way would that have happened if MS still had VB classic. In the past,we sold about a thousand MS OS licenses (that's £80K we gave MS .. not bad for an SME). One of our biggest sellers was a protocol converter.. A PC that just took an input stream and produced different output. Obviously that should be embedded, but we just thought turn a quick buck, bung in MS and a VB6 app. Not now. All Linux, Python. MS are traitors, pure and simple. I invested decades of experience and refined skill, and they trashed it all out of caustic malicious bad management followed by a display industrial levels of ignorance and arrogance. I looked at an MS tablet the other day and thought.. hmm, well I still do know MS better than Linux etc, maybe I should put VB6 on that.. Then I remembered the betrayal and thought NEVER AGAIN. The law should never allow an influential company to capture a skill, then deny a person his own skill through patent & copyright abuse. Quite disgusting behaviour on every level -- moral, ethical and business-wise. NEVER FORGET.

      • MichaelMichael commented  ·   ·  Flag as inappropriate

        You wonder what kind of company would kill active development on a development system while it has enormous industry impact. Loved by a huge demographic of developer and clients alike. Works on every major OS the company makes. Now we know.

      • EdEd commented  ·   ·  Flag as inappropriate

        Based on I Microsoft's latest post on this forum of declining our requests I am going to have a preliminary meeting with my management and inform them that, despite the communities best efforts to change it (VB6), Microsoft's business model is strictly revolutionary as opposed to evolutionary.

        That is , any technology we invest in with them for development will be killed at some point. This is opposed to the Open Source model of most development systems available where any technology is perpetuated indefinitely. As long as developers and clients feel it meets there needs.

        We need to start making plans to get off any Microsoft development platforms and move to Open Source.

        With the new Microsoft management, should they change their model in the next 6 months to that of the rest of the industry we'll realign with them. Otherwise lets move forward.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        This can only mean that we can't stop with the fight and persistence! In fact, we need to fight more!

      • RobyRoby commented  ·   ·  Flag as inappropriate

        Microsoft does not deserve loyalty ..... it tramples our work .... I and my group we switched to RAD Lazarus (FreePascal) and we work very happy and serene !!!

      • Anonymous commented  ·   ·  Flag as inappropriate

        Though Microsoft killed the widely used VB6 as COM based development langugae, a large amout of header files still exist in Windows SDK and VC++. unfortunately, almost all vb6 releated components have been gone in x64 from the start, I.E., in a x64 version office VBA, you can not even display a "Color" or "Font" property page for a control, because it's a VB6 component and MS did not port it to x64. while "msstkppg.h", the header files for stock properties, just compiles when writing an Activex control targeting x64 platform, but not for run, because it only return class not registered HRESULT.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Sorry people for the formatting, it came out lousy.

        Hman2828... Your readind is about as good as your logic. For one thing, only the first and last paragraph were quotes.

        Then.. wait a minute... just imagine I want to write an app to the phone platform whose code would be : print "Hello world", where in h*** do you think I want it sent to ??? to stderr piped to your a** ????

        I kwnow it's not easy question for narrow minds but i'll give you two clues to help figure this one out : Phone, World.

      • HMan2828HMan2828 commented  ·   ·  Flag as inappropriate

        >> In my view, there is no reason WHATSOEVER for which you could not write the "Hello World" app for any platform anymore complicated than a simple : print "Hello World"

        1- You want to "print" where exactly? On screen? On printer? On an external device? To file? To the console? StdErr or StdOut?
        2- Debug.Print("Hello World") is not very complicated, and prints to the debugging window. Or Console.WriteLine("Hello World"). Once you figure out how to work in an proper objective way, you quickly realize what is going on.

        >> OK, so MS fanboys can revel in their C++, C# or .NET, why not a parallel product? I am just saying here, out of my head ... let's call it : VB7-64 bits. My bet is that it would outsell in a flash any of the VS products.

        And what will you use this VB7-64 for? As was said countless times, 64 bits gives you nothing. A 64-bits app could only compile against 64 bits components. So basically VB6 64 bits = goodbye COM and ActiveX. Goodbye all the 32-bits components you bought. And it will not sell in a flash precisely because most people know that tagging "64 bits" at the end gains you nothing at all.

        >> Actually, I don't only see it as an alternative, but rather as a Golden Opportunity to get back to bases, and re-engineer the product almost from scratch, keeping of course its governing principles and easy syntax while aiming at the same time at platform portability.

        So, you can't be bothered to learn the new one, and you want everyone to devolve to your level? I see a Golden Opportunity (tm) for you to get back to the bases and re-engineer your career almost from scratch, while of course keeping your simple syntax and ideas.

        >> Who can tell where and what VB6..7.. could do nowadays if development had been put on it at the same rate as the hit-and-run (and flee the scene)

        Pretty sure it's one of those situations where it doesn't matter which road you take, they all lead to the same place. The improvements made to VB in .NET were not just randomly picked out of a hat. They were programming concepts that had been around for years in other languages, and that needed to be integrated. So even if you were to go back in time, and relive the dev cycle that brought VB6 to become VB.NET a thousand times, I doubt the outcome would ever be different.

        >> dreams with OOP and polymorphism, there are hundreds who simply need to fire an IDE and write a custom spreasheet for their office, or a bill

        So then just fire up Access and plow away. That what VBA is for.

        So now I realize you are just posting someone else's comment. You are lucky! That guy clearly is not very bright.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Excerpt from a Win10 TP exchange about Win 10's ugliness.

        srfreeman wrote :

        "As I've mentioned before, Windows like anything else is a product sold by a business. It is the responsibility of the business to built a product

        that their consumers want. If customers are saying they are not interested without these customizations available, then there is no argument to be

        made. Microsoft has only three choices: Lose the customers, hope they will invest in all those third party utilities, or give them what they want.

        While you may find the 2nd approach viable, many other people do not. I prefer my system running with minimal modification. The ability to have

        everything I need out of box without modifying system files or installing tons of extra system services to hijack various operations on the system is

        more than just convenient to me..."

        .Net is to VB6 what Win 10 is to Vista/Win7 users : an ugly duck!

        As a business principle, a company ought to bring consumers the product they want. In many business schools, that would be the number one rule for

        success.

        MS is doing some of that : in VS, you got your C#, C++, VB, use whatever you prefer. But the Classic VB way of doing things is gone. Of course, VS has

        a few tricks easier to do than VB6, but that is only because MS has been putting their money on the framework only for now ohhh so many years. And

        they are pretty much s*** deep into it to recognize that a vast number of people just don't like those managed languages. It's not a secret that

        internally, the OS people loathe managed code, and that there is nothing wrong with COM (windows is mostly COM, framework more like a layer on top) if

        it benefits from continued development. The Windows kernel (low level api, gdi, MCI, COM) MS will never be able to get rid of and may very well outlast framework and managed code. If that's the case, come Win 11, 2018, 2024 and well after that, VB6 could still be a desired option for which it will not be wise to end support. Industry likes long lasting standards... CNC machining is still being done with HPGL or G-Code engineered in the seventies, just like a car still has four wheels, and for a simple good reason : IT WORKS!

        Who can tell where and what VB6..7.. could do nowadays if development had been put on it at the same rate as the hit-and-run (and flee the scene)

        products MS has been serving for years (obsolete framworks that will still need be supported, Win RT, Silverlight, etc.)

        It was once Bill Gates's own vision that one day, Windows apps would be as easy to write as a basic program was back then. And that path was followed

        for a while (VB6). But then the world crumbled and what was to follow only succeeded in putting programming out of reach of the masses. I don't doubt

        that some programmers at system level want and need something real powerful (OOP and it's paradigms) etc.. but for one techie that wants to wet his

        dreams with OOP and polymorphism, there are hundreds who simply need to fire an IDE and write a custom spreasheet for their office, or a bill

        calculation, or... the list is endless.

      • Anonymous commented  ·   ·  Flag as inappropriate

        (continued)

        To all these people, MS is saying : NO. You want the Windows programming experience? Be ready to feel the pain.

        Look at simplest way to write a Metro APP. Borderline ridiculous : lots of very advanced computer topics you have master before even doing the simplest thing.

        In my view, there is no reason WHATSOEVER for which you could not write the "Hello World" app for any platform anymore complicated than a simple :

        print "Hello World"

        VB6 can do that with the less amount of effort in Windows history. A true RAD. Wake up MS, this is what we expect from you : write a compiler where

        YOU take care of the nitty-gritty, and leave us, common mortals, more time to achieve productivity and write products instead of being swamped by the

        complexities of the programming system.

        With it's constant change of directions, MS, the very company that writes the OS is trailing the pack as far as writing portable applications is

        concerned. IE is the worse of the browsers. It's laughable really. Better watch out if someday, Google or Java decides to venture into the OS

        business.

        OK, so MS fanboys can revel in their C++, C# or .NET, why not a parallel product? I am just saying here, out of my head ... let's call it : VB7-64

        bits. My bet is that it would outsell in a flash any of the VS products.

        Actually, I don't only see it as an alternative, but rather as a Golden Opportunity to get back to bases, and re-engineer the product almost from

        scratch, keeping of course its governing principles and easy syntax while aiming at the same time at platform portability. Truth is VS has become a much too big animal, and admit it MS, you barely have the resources and qualified staff to continue mantaining and growing this thing much longer and keep up tying up the loose ends.

        Oblivion is menacing a company that does not fullfill the real needs and desires of it's user base, much less acknowlodging them. Win 8 was lesson... a while back NASA was served a lesson too, comittees concluded a CHANGE OF CULTURE was the biggest element to bring about solutions for their problems. I find the term wholly appropriate to the situation at MS.

        Later on , srfreeman writes and concludes :

        "The current state of affairs paints a bleak picture for the part of the IT world represented in this thread. As Windows 10 becomes a continual work

        in process, it seems that the stream of complaints will only be stemmed through attrition in the ranks."

        Feels like déjà vù!

      ← Previous 1 3 4 5 58 59

      Feedback and Knowledge Base