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!
Good question. I was quite annoyed they removed the ability to do DirectX onto a PictureBox back in the DX9 days...all to push WPF... The only point of taking away features is to force a paradigm no one really wanted. They should have spent the time to redo the WinForms back-end back then so that WinForms controls were essentially 'dumbed-down' versions of WPF controls...but no... So now we have MAUI...
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#.
What is there to extend in VB? The language is basically perfect. What I have been seeing is C# gain VB features. I think when they added lambda functions to VB to try to be like C# it bastardized the language somewhat. Also LINQ syntax is kinda crappy too...I try to never use it myself. Meanwhile C# programmers think they are so cool because they can do "is null" now, LOL! So yeah - I'm just annoyed there isn't a VB-Blazor project template etc...
@@loudfiero I also had a good laugh when they introduced "is null" to C# :-) Do you know if you can create a C# Blazor project from template and convert it to VB and it works? In ASP.NET Web Application (.NET 5) I did so and it worked. I converted it with: github.com/icsharpcode/CodeConverter
Great to see winforms is being expanded, but is there any plan for any web based vb solution support?
My favorite langage since VB 3.0
Long live VB!
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!
Were the graphics in the last app created solely with VB and .NET 5, or were you using a third-party graphics package?
Good question. I was quite annoyed they removed the ability to do DirectX onto a PictureBox back in the DX9 days...all to push WPF... The only point of taking away features is to force a paradigm no one really wanted. They should have spent the time to redo the WinForms back-end back then so that WinForms controls were essentially 'dumbed-down' versions of WPF controls...but no... So now we have MAUI...
What everybody really wants is VB-Blazor! I mean what's the point of replacing Javascript with another C-syntax language...?
Luckily you can write a single line of C# and just branch to VB ! But you are right, it would be even better if you have VB-Blazor.
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#.
an experienced VB programmer uses C# and C++ just as an add-on, but there's no reason to be different.
It was about damn time...
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. :(
What is there to extend in VB? The language is basically perfect. What I have been seeing is C# gain VB features. I think when they added lambda functions to VB to try to be like C# it bastardized the language somewhat. Also LINQ syntax is kinda crappy too...I try to never use it myself. Meanwhile C# programmers think they are so cool because they can do "is null" now, LOL! So yeah - I'm just annoyed there isn't a VB-Blazor project template etc...
@@loudfiero I also had a good laugh when they introduced "is null" to C# :-) Do you know if you can create a C# Blazor project from template and convert it to VB and it works? In ASP.NET Web Application (.NET 5) I did so and it worked. I converted it with: github.com/icsharpcode/CodeConverter
@@loudfiero an experienced VB programmer uses C# and C++ just as an add-on, but there's no reason to be different.
We need VB intellisens with vscode...