VB.NET isn’t all that uncommon - it isn’t exactly Fortran, and it’s still maintained by Microsoft. I know a senior engineer that still writes a lot of new code in VB.NET because he’s just used to it…
It is not, and I’ve heard of people preferring it even. Just not me. In my eyes, it’s just a worse version of the C#.NET aspx views that might make OC shudder again.
Maybe more to your tastes, we also still have COBOL systems. Not quite Fortran old, but close
It’s the same normal view / control pattern but with VB for the logic instead of C#.
There’s also global pages with a bunch of events like error or pre/post request that probably exists in the C# version I guess, but I only remember dealing with it in VB
This particular system also comes with a pure VB batch script running on a schedule.
Just very old, frustrating to deal with, slammed in security audits.
Ooh then I have a good campfire story for you.
I know of a company who still has a VB.NET app running.
There used to be more just a few years ago, but I’ve managed to get them to let me modernize most of them.
VB.NET isn’t all that uncommon - it isn’t exactly Fortran, and it’s still maintained by Microsoft. I know a senior engineer that still writes a lot of new code in VB.NET because he’s just used to it…
It is not, and I’ve heard of people preferring it even. Just not me. In my eyes, it’s just a worse version of the C#.NET aspx views that might make OC shudder again.
Maybe more to your tastes, we also still have COBOL systems. Not quite Fortran old, but close
deleted by creator
Isn’t VB.Net just .Net with weird syntax for the loops and ifs?
Pretty much. .NET 4.7.2
It’s the same normal view / control pattern but with VB for the logic instead of C#.
There’s also global pages with a bunch of events like error or pre/post request that probably exists in the C# version I guess, but I only remember dealing with it in VB
This particular system also comes with a pure VB batch script running on a schedule.
Just very old, frustrating to deal with, slammed in security audits.
As an Australian, I understand what happened. They were all drinking VB while coding it.
Its not even that interesting. Working with Visual Basic is coding with all the fun sucked out of it.
OoooooOOOOOOooooo…