Visual Basic support planned for .NET 5.0

.NET Team

.NET Team

We’ve heard your feedback that you want Visual Basic on .NET Core. Earlier versions of .NET Core supported Class Library and Console applications types. Starting with .NET 5 Visual Basic will support:

  • Class Library
  • Console
  • Windows Forms
  • WPF
  • Worker Service
  • ASP.NET Core Web API

We are supporting these application types to provide a good path forward for the existing VB customer who want to migrate their applications to .NET Core. This allows Visual Basic customers to take advantage of new platform features like side-by-side deployment, cross platform support, performance and new API improvements.

One of the major benefits of using Visual Basic is that the language has been stable for a very long time. The significant number of programmers using Visual Basic demonstrates that its stability and descriptive style is valued. Going forward, we do not plan to evolve Visual Basic as a language. This supports language stability and maintains compatibility between the .NET Core and .NET Framework versions of Visual Basic. Future features of .NET Core that require language changes may not be supported in Visual Basic. Due to differences in the platform, there will be some differences between Visual Basic on .NET Framework and .NET Core.

If you are happy with .NET Framework, you can be confident that it will remain supported as long as Windows is supported because it is shipped with the OS. Both Visual Basic and C# customers can continue to use .NET Framework and need to port to .NET Core only if you want features like those listed above. If your application uses technologies that aren’t supported on .NET Core, like WebForms, Workflow or WCF, you might want to stay on .NET Framework because porting will require work to move to newer technologies.

Visual Studio regularly adds new features to improve the experience for developers, including those using Visual Basic and either .NET Core or .NET Framework. An example is the recent addition of IntelliCode for Visual Basic.

Visual Basic is a great language and a productive development environment. The future of Visual Basic will include both .NET Framework and .NET Core and will focus on stability, the application types listed above, and compatibility between the .NET Core and .NET Framework versions of Visual Basic.


Leave a comment

  • Avatar
    Cristian Luis Teixeira

    Really really weird! has a very readable syntax which is exactly what is leading Python to be the dialect number 1

    Microsoft has a dialect that could compete with Python, but prefers to abandon it, which ROI and / or malice is capable of doing with an excellent product like

    The VB family (VB6; VBA; VBscript and never died, the VB family was always murdered!

    everyone who is still interested in buying anything from Microsoft has to ask the following question:

    How long will the product last;

    How long will Microsoft keep you competitive;

    And if you have a commitment contract guaranteeing everything.

    Long live the VB family that I think could be called VB ++

  • Avatar
    Cristian Luis Teixeira

    After so long we started to have signs of falling from in the TIOBE index. – (But Microsoft’s lack of respect and commitment to VB is sure to affect its reputation in other products.)

    The VB family I should call VB ++ never died, it was always murdered!

    See the example of VB6 is a dialect ahead of its time, requires much less ceremonies and paraphernalia (it was discontinued and VB net too) but ROI is in charge in the world. If the money is where we can complicate then why make it easy? see the market that languages ​​derived from “C” generate, much more doubts, consequently more need for paid support, more courses to be sold and so on. Evolving a language that is easy to understand is to cure a sick person but the best deal is to sell medicine.

    If a lie is repeated by everyone several times then it will become a truth.

    Python is the best ===== modinha

    Descendants of “C” is the future ==== so it will be!

    “Microsoft with this attitude that you have every day of turning everything into a legacy, soon no one else will believe you, so the legacy will be Microsoft itself.”

    Can you imagine a group of professionals saying that Mirosoft is not reliable and the best thing that any professional should do is to use another non-proprietary company? what will happen? if a lot of people in the world speak repeatedly it will become true.

    Keeping a team of two to three people dedicated to seems to me to be smarter and cheaper than facing an image crisis by people who will say that Microsoft is unreliable and does not respect its customers very well because of ROI . It is a very small cost to avoid such great wear.

    Respect VB6,, VBA customers more, after all the VB family has always been a success for Microsoft!

        • Avatar
          Cristian Luis Teixeira

          really Microsoft is murdering

          all innovations are restricted to C # and F # only.

          Even though F # is of a much smaller magnitude, they are receiving due respect.

          with VB it’s really a murder!

          • Avatar
            Francisco González Venegas

            I think all developers around the world hate Microsoft except Visual Basic developers, Microsoft hate Visual Basic developers, .NET Team is insane or something worst.

  • Avatar
    Jens Samson

    The silence gets more deafening every day. The last anouncement was made on March 11th, we’re almost 9 months later, the time it takes for a baby to grow, .NET 5.0 has been released, but still nothing.
    What have you guys been doing for the last 9 months ? Do we not at least deserve some feedback ?

  • Avatar
    hitesh davey

    Dear VB Guys,
    C# 9 language features are not that difficult to implement in VB.NET (as projected by the MS team) but MS made it very clear that they are not going to invest further in enhancing the language and VS tooling support. If you are still hopeful about MS will listen to your voice then you are beating a dead horse!

    More than MS, we invested more in in terms of time, efforts in learning, developing, & maintaining the app. We believed in MS’s fake promise to keep the VB.NET language as a first-class citizen. We have hit on our own foot.

    Not enhancing the language and VS tooling support is a clear indication that MS is discouraging all VB developer to stop using VB on the .Net Core platform.

    I am afraid about the next release of .NET. Ver 6 will introduce breaking changes to an extent that VB will become incompatible to take advantage of .Net 6 features.

    • Avatar
      Cristian Luis Teixeira

      if i have to learn a new programming language it will certainly not be from Microsoft, i no longer trust this company, for me the legacy is Microsoft itself.

      I am a customer, above all I am a BASIC customer, if I cannot be here it will be elsewhere!

      just to name a few B4X possibilities; VBMercury; Xojo; RADBasic.

  • Avatar

    微软承诺在.NET5.0中支持 ASP.NET CORE WEBAPI,为什么官方没有提供,开源社区中提供的工具都能支持了,提供一个模板就这么难吗?在6.0版本中才支持吗?为什么不添加对移动开发的支持?

  • Avatar
    Cristian Luis Teixeira

    I wish a HAPPY NEW YEAR to all lovers, supporters, developers and communities of our beloved programming language VISUAL BASIC.

    I want a HAPPY NEW YEAR SPECIAL TO YOU VB and that in 2021 you can continue giving us a lot of joy, competence, productivity and satisfaction, I wish you a full year and evolution and continuity! Never forget, you can always count on me I LOVE YOU VISUAL BASIC.

  • Vb Wyrde
    Vb Wyrde

    VB.Net is easier to code and maintain than #C because of the following reasons:

    1. Case Sensitivity. In C# you have to carefully watch every variable name to ensure that you do not accidentally use the wrong case. In VB.Net you never need to worry about that as the IDE fixes the case for you. Screwball errors related to case are not possible in VB.Net.

    2. Syntactical Doodads. In C# you need to use {} and ; in order to segment your code blocks. In VB.Net you need only drop to the next line. This makes the code in VB.Net less verbose, and easier to read, and introduces few places where a missing doodad could cause problems.

    3. Plain English Syntax. Visual Basic has always been focused on Plain English Syntax from the beginning in order to make the language easier to learn, easier to code and easier to read. C# … not so much.

    Overall, VB.Net is bound to produce fewer coding flaws because of these three aspects. The increased chance of errors in C# due purely to design features such as case sensitivity will naturally aggregate into a higher failure rate for C# software vs. VB.Net.

    VB.Net is easier to code, easier to learn, and easier to read. Why Microsoft wants to eliminate this superior language is a mystery. I would recommend Microsoft reconsider. Stick with your strengths. Visual Basic was what made Microsoft the predominant company it became because many corporations calculated that the ease of development meant a higher ROI for their internal development teams. It was the ease of use that made it a winner. Don’t abandon that principal, Microsoft. It has won you a top tier position. Maintain your position. Support VB.Net.

    In addition, originally Microsoft promised that the .Net framework would support VB.Net and C# equally. Keep your promises, Microsoft. You’ll be glad you did.

  • Avatar
    Cristian Luis Teixeira

    Well, well, the .NET Team took the time to come here and delete the previous comments and didn’t have the time and courage to really be clear about VB.NET.