Supporting VB.NET in .NET 5

In this episode, Rich is joined by Merrie and Klaus who walk us through some of the new capabilities available for VB .NET developers building WinForms applications

[00:00] - Intro
[01:10] - What’s the relationship between WinForms and VB?
[02:24] - What was needed to get VB .NET support working?
[04:52] - Benefits of moving your VB .NET apps to .NET 5 (Demo)
[12:34] - Making user of Win10 device sensors (Demo)

What's New in Visual Basic on .NET 5?

Walkthrough: Calling Windows APIs (Visual Basic)

Windows Forms documentation

Visual Basic documentation

Walkthrough: Calling Windows APIs (Visual Basic)

#DotNet #VisualBasic #WinForms

[calvinwilson]

Great to see winforms is being expanded, but is there any plan for any web based vb solution support?

[cristianluisteixeirafrc]

Yes, I understand that VB doesn't really need to follow the same steps as C#, but the world of VB is big enough to handle WEB and Mobile development as well.

Some technologies where VB was omitted after MVC 5 can be overcome if VB is part of MAUI.

I really appreciate stability with changes that make sense without being related to fads, I don't see the need for the VB developer to go through a lot of trial and error and hits with new tools all the time, like in C#.

I also see that C# is in a way I wouldn't want VB to be, C# will soon stop being a dialect of knowledge for the whole team, just like it is in C++, C# will not be readable for everyone involved in a project, and I really don't want that same path for VB.

VB needs to be in Desktop, WEB and Mobile scenario with efficient tools and RAD, RAD is the culture of VB!

We have a great path for winforms, we need a path for WEB and Mobile, even if it's just one path, but that path needs to be available for VB developers.

We need MAUI Yes!

[loudfiero]

What everybody really wants is VB-Blazor! I mean what's the point of replacing Javascript with another C-syntax language...?

[wesdick]

Were the graphics in the last app created solely with VB and .NET 5, or were you using a third-party graphics package?

[mayurbanta]

The only incentive of moving VB.Net to .Net 5 is porting of legacy applications in to new framework. There are many companies who are earning millions from old solid VB.Net applications and they do not want to change it. They'll be happy to move to .Net 5 so that they can integrate newer features, of course written in C#.

[tmhchacham]

18:37 I think we will see a lot of more things around Visual Basic. It's not particular that we will extend the language itself so much....

So sad. :(