I suggest you ...

Rename Visual Basic to B# and Support B# With Absolute Parity

Dotnet 2015 made it clear: VB.NET developers need to switch to C# or be left behind. Very sad.

VB syntax is friendlier, easier to read and code and maintain. Yet Microsoft is killing off this superior language bowing to pressure from myopic C# developers and Mono.

346 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Century shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    45 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Leroy "Spydaz" Dyer commented  ·   ·  Flag as inappropriate

        Perhaps it should be renamed to B#
        Visual basic.NET is a fine piece of Programming language. The journey from VB6 was actually slow, but once started i have never gone back , except to Extract old code.
        There is a VB6 Extension in VB2015 Allowing you to open projects in visual studio 2015. Although it works best when Visual Studio 6 Enterprise is also installed.

        But i understand that Attracting a NEW Generation of Programmers is not an easy task so a name change maybe relevant to this generation. Although VB.NET is Fine with me!

        I would request that Visual-Basic be kept in the .Net framework as no language Should be sent to its death when it is so widely used;
        Personally i do not like the C# Style or the Java Style or the C++ style. the Only Competition VB.Net has is Python! and that would be a step backwards . Yes C# has everything that visual basic has, but its style is very JAVA where Basic is the original Very readable and Understandable Code even for non programmers. this is actually why its so successful.
        SYNTAX!
        I have recently looked at my VB6 programming and there was so many Errors that the compiler did not pick up it was very forgiving. VB.net have got it completely RIGHT!.....

        But if people Still Would like to use VB6 perhaps it should be able to be downloaded for FREE. But limited to its .NET framework cutoff. and as the dot net frameworks aims to be compatible for its legacy applications perhaps all the controls could be bundled into a Single Control Which would be in all distributions of .NET? for those wishing to use the Old style controls and Language could use Microsoft CODE? or even the VB6 Extension in Visual studio to write visual applications in the newer planned versions of Visual studio.

        I still use VB2015 and this is because upgrading projects has been so bad! and microsoft have not given free upgrades to full license of VB2015 and i would have to use the community edition!
        I would hope that features offered to visual studio 2017 users would be included in updates to vb2015....

        i would hope that visual basic.NET is maintained ! as well as VB6 made available to be used for those stuck in the past. I urge those people to Try to move forwards as the VB.NET is better! and not so hard! i'm always amazed by the paradigms it contains and the hidden features (as well as the old commands still available)

        VB.NET (HIGHLY ROBUST)

      • Damon commented  ·   ·  Flag as inappropriate

        That's because Microsoft abandoned Visual Basic and tried to replace it with the poor VB.Net. No surprise it isn't popular.
        VB6 programming was always far more popular, and probably still is.

      • Microsoft, update VB6 programming & VBA programming commented  ·   ·  Flag as inappropriate

        Good news that Microsoft have extended support of VB6 to Windows Server 2016. VB6 programming is supported until at least November 2027 on Windows Server 2016, and until at least 2025 on Windows 10. Both are likely to be extended.

        Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1, Windows Server 2012, Windows 10, and Windows Server 2016
        https://docs.microsoft.com/en-us/dotnet/articles/visual-basic/reference/vb6-support

        VB6 programming is supported on Windows 10, Windows Server 2016 and earlier versions of Windows.

        VBA programming is supported on Office 2016 and earlier versions of Office.

        VBScript programming is still part of Windows.

      • .Net is failing commented  ·   ·  Flag as inappropriate

        The 2017 Stack Overflow survey is very interesting...

        C# has fallen in popularity from 45% to 34% in just 5 years.

        It is amazing to see how far C# has fallen in the last few years.
        C# was intended to compete with Java but was never successful in that.
        It is unlikely that C# will still be a mainstream language in 5 years time.

        And Xamarin is one of the most dreaded technologies in the Stack Overflow survey.
        Never successful as an independent business, Xamarin is now failing in Microsoft's ownership.

        https://stackoverflow.com/insights/survey/2017/?utm_medium=email&utm_campaign=dev-survey-2017&utm_content=em-features&utm_source=so-owned

      • Anonymous commented  ·   ·  Flag as inappropriate

        @Ray Koopa

        >>Too bad you didn't even understand why the C# name has a # in it. Very sad.

        Do tell us. I certainly have no idea. Obviously nothing to do with speed either of development or performance.

        Is it C-hash because Microsoft made a hash of it ?

        It is more D-flat than C-sharp.

      • ARM brings back VB6 programming commented  ·   ·  Flag as inappropriate

        Good to see that VB6 programming will run on ARM processors under full Windows 10.

        You'll even be able to run the VB6 IDE on an ARM tablet.

        dotNet will be too slow on ARM processors, so a great future for VB6.

      • Rashid Ali commented  ·   ·  Flag as inappropriate

        Just because of the name. There is a common perception that C# is more powerful than VB. Which is totally wrong. No more Visual Basic B# B# B# B# B# B# B# only.

      • Zagor Tenay commented  ·   ·  Flag as inappropriate

        Microsoft have already announced VB.Net will no longer have parity with C#.

        Microsoft is killing off VB.Net.

      • HMan commented  ·   ·  Flag as inappropriate

        Where did this "VB.Net is being abandoned" even coming from anyway? Was there an announcement I missed?

      • HMan commented  ·   ·  Flag as inappropriate

        Hum, no.

        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 simply wasn't viable to migrate this to .Net. Migrating to C# is a dead end, now that .Net doesn't have a long term future.

        What is really needed is migration to an updated VB6 programming language, for both our VB6 source code and our .Net code. This would be compatible with VBA programming and would carry our VB6 programming skills forward.

      • Anonymous commented  ·   ·  Flag as inappropriate

        It is time for MS to abandon VBdotNet and bring out an updated VB6 programming language.

      • Jay commented  ·   ·  Flag as inappropriate

        The language name doesn't matter and friendlier is subjective but I agree 100% that there needs to be parity. I switch between languages easily enough depending on whichever language my clients prefer but to not have the same tools available in each language is a huge productivity killer.

        For example, you brought back "Create Unit Test" in C# but skipped VB, EVEN THOUGH THIS FEATURE USED TO BE IN VB!!! Releasing this to one language but not the other is simply lazy if not evil.

        Anyone in Microsoft that still thinks one of these 2 languages is superior to the other is a fool. The overwhelming bulk of the work real .Net programmers do revolves around the common core classes and .Net Framework with C# or VB syntax being the glue used to connect those pieces, far less than 1% of the work. It shouldn't matter which language we use. Stop giving parity lip service when it comes to Visual Studio tooling!

      • Jon McRae commented  ·   ·  Flag as inappropriate

        I'd like to try the Community Edition of .Net but many of us cannot place an app server anywhere near the Internet without the security folk gett'n all riled.

        Please vote for this to give us an option to register it offline or put out a true Open Source version with no reg. Thanks.

        http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/9563619-enable-vs-community-activation-registration-offlin

        Mean time gonna keep us'n VB6...

      ← Previous 1 3

      Feedback and Knowledge Base