I suggest you ...

make it easier. In VB6 i don't have to know what classes are. It has been to complicated for simple programms.

180 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
leo shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

20 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Microsoft, update VB6 programming & VBA programming commented  ·   ·  Flag as inappropriate

    Microsoft's support statement for VB6 programming...

    Support Statement for Visual Basic 6.0 on Windows
    - updated with Windows 10 version 1709 support information.

    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 10
    Windows 8.1
    Windows 7
    Windows Server 2016
    Windows Server 2012 including R2
    Windows Server 2008 including R2

    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.

    The VB6 runtime will ship and will be supported in Windows 10 for the lifetime of the OS (that is until at least 2025).
    The VB6 runtime will ship and will be supported in Windows Server 2016 for the lifetime of the OS (that is until at least 2027).

    https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-basic-6/visual-basic-6-support-policy

  • Damon commented  ·   ·  Flag as inappropriate

    It has always been more practical to use VB6 programming than the overcomplex .Net.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Now that VBdotNet is being slowly abandoned there is no reason to do this.

    It is better to use the VB6 programming language.

    THE VB6 runtime is included in Windows 10
    https://docs.microsoft.com/en-us/dotnet/visual-basic/reference/vb6-support
    https://github.com/dotnet/docs/blob/master/docs/visual-basic/reference/vb6-support.md

    And the VB6 IDE installs on Windows 10
    http://nuke.vbcorner.net/

  • Anonymous commented  ·   ·  Flag as inappropriate

    Microsoft is bringing full Windows 10 desktop apps to ARM processors.

    Good news for VB6 programming.

  • Open Source VB6 programming commented  ·   ·  Flag as inappropriate

    VB6 is far from dead.

    Microsoft say "the Visual Basic 6.0 IDE is available to all MSDN subscribers and can be downloaded at any time from the subscriber downloads section and installed. A generic subscriber key is provided for convenience if needed."

  • Open Source VB6 programming commented  ·   ·  Flag as inappropriate

    Microsoft say "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."

  • dhfask commented  ·   ·  Flag as inappropriate

    "And seriously, that question above is as stupid as they come. "Make electrical engineering easier, I don't know what a volt or an ampere is, I just want to do simple electricity!""

    It's just another example of how stupid the VB6 spammers are. Since their dead-for-20-years language is not coming back, all they can do is complain about how difficult vb.net and c# is.

  • Anonymous commented  ·   ·  Flag as inappropriate

    VB.Net no longer keeps up with C#

    Microsoft are slowly abandoning VB.Net

    Time to bring back the VB6 programming language, either as an updated version or as open source.

  • Spam Alert commented  ·   ·  Flag as inappropriate

    SPAM ALERT !
    HMan, the VB.Net obsessive is posting again. Get over it, HMan, VB.Net is dying.

  • HMan commented  ·   ·  Flag as inappropriate

    And seriously, that question above is as stupid as they come. "Make electrical engineering easier, I don't know what a volt or an ampere is, I just want to do simple electricity!".

    Programming is a computer SCIENCE. It requires participants to learn new things every now and then, forever and ever until the end of time. If you can't be bothered to take a class or read a book, I don't think that is anyone's problem but yours.

  • HMan commented  ·   ·  Flag as inappropriate

    Riiiight...

    This is a post from the MS program manager for the VB team, Anthony Green, from January 2016:

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/53619f54-8593-4563-955f-7642b983222f/future-of-visual-basic?forum=vbgeneral

    Re: VB has a long future ahead of it no matter how you look at it. We're working on the next version – the 25<sup>th</sup> Anniversary version – VB15. Visual Basic is an open source language (check us out on github) so it can't really be killed even in the event of Mount St. Helens erupting and burying Microsoft campus in magma.

    So... yeah.

  • Bring Back VB.Net commented  ·   ·  Flag as inappropriate

    Now that VB.Net has been downgraded to a second-rate language and won't be updated very often there is little chance of this request being met.

    VB.Net is being abandoned.

  • Faisal commented  ·   ·  Flag as inappropriate

    Microsoft need to tell us the route forward. If they have one.

    The adoption of the VB.Net language was a mistake, now we need to migrate our VB.Net code. And we still have VB6 code, it wasn't viable to migrate this to .Net.
    Migrating to other Microsoft languages like C# is a dead end, now that .Net doesn't appear to have a long term future.

    We need migration to an updated VB6 programming language, for both our VB6 source code and our VB.Net code. It would keep compatibility with VBA programming and would utilize our VB6 programming knowledge.

  • Invader g commented  ·   ·  Flag as inappropriate

    I'd go back to an updated VB6 immediately if there was one. It was far more productive than the bloated .Net

  • McZ commented  ·   ·  Flag as inappropriate

    In VB6, any Form is a class with the nastiness of a default instance. A ADODB-recordset is a class. Any COM-Object is a class.

    Honestly, what "program" could this be?

    TEST 1
    In VB6, you start a new exe-project, press F5, form shows.
    In VB.NET, you start a new WinForms-project, press, F5, form shows.

    TEST 2
    In VB 6, you add a button, double-click and write handler-code.
    In VB.NET, you add a button, double-click and write handler-code.

    TEST 3
    In VB 6, you create an ADODB-connection, a recordset and retrieve data through calling Open.
    In VB.NET, you create a OleDB-connection, a command and retrieve data through calling ExecuteReader.

    How is this "harder"?

Feedback and Knowledge Base