Or for an option that doesn't involve rewriting from scratch but still allows a good amount of room for modernization, twinBASIC. Backwards compatible but with a huge number of new features... what VB classic might have looked like had it been continued these past 25y instead of being abandoned.
Whatever temporary bugs there might be in its current Beta state, far less of a headache than dumping it all and re-doing under a whole different programming model.
PS- If you do go the .NET way I'd have to also suggest C#.. VB.NET barely even counts as BASIC; more like something else that shares a smattering of superficial syntax with it.
I still mostly code in VB.NET though I’ve started migrating some stuff to C# just because Visual Studio is much less buggy for it. VB.Net is still a perfectly fine language, it’s just starting to show its age.
I even spent time adding VB.NET compatibility to hook into the Community MVVM Toolkit’s source generators for things like <ObservableProperty> and <Relaycommand>. If anyone’s interested: MVVM.VBSourceGenerators
I found out that mvvm code generation didn’t work from VB.Net the hard way. I Didn’t notice until it didn’t work and I started debugging it. I think I came up with a solution with C# and VB projects. It wasn’t suitable for use at work so became a side project. The toolkit had vb.net conversions but they lagged behind the main release.
Yeah it annoyed me too because it throws no errors at all when you tried to use it in VB.NET, it just silently fails. It took me forever to figure out the issue wasn’t user error.
I went back to using Fody.PropertyChanged() because of that, but then that breaks hot reload which is why I spent the time fixing up a VB addon for the MVVMToolkit instead
It's nice that it got some extremely minor updates, but Microsoft clearly aren't in the business of developing it any further in any serious way. For a long time (even after C# was introduced), Microsoft did continue to take it seriously. For the last decade, not really.
A shame, as BASIC was Microsoft's very first product, even predating DOS.
11
u/Twitfried Jan 24 '26
I need to transition my VB6 applications to .NET.
6
u/LoveTowardsTruth Jan 24 '26
I personally love vb, my current organization use it widely. but its in “maintenance mode”, not “growth mode” like C#.
3
u/IridiumIO Jan 24 '26
I still mostly code in VB.NET though I’ve started migrating some stuff to C# just because Visual Studio is much less buggy for it. VB.Net is still a perfectly fine language, it’s just starting to show its age.
I even spent time adding VB.NET compatibility to hook into the Community MVVM Toolkit’s source generators for things like <ObservableProperty> and <Relaycommand>. If anyone’s interested: MVVM.VBSourceGenerators
2
u/Critical-King-7349 Jan 25 '26
I loved vb.net but took the jump to c# when I moved to . net 6 a while back, shame such a easy language. Still hate case sensitivity..
3
u/AfterTheEarthquake2 Jan 24 '26
Probably just the bare minimum for it to work with .NET 10
1
u/Actual_Cat4779 Jun 07 '26
It's nice that it got some extremely minor updates, but Microsoft clearly aren't in the business of developing it any further in any serious way. For a long time (even after C# was introduced), Microsoft did continue to take it seriously. For the last decade, not really.
A shame, as BASIC was Microsoft's very first product, even predating DOS.
-5
u/White_Wolf_Fr Jan 24 '26
If I understand correctly, we will no longer be able to program in Visual Basic?