FYI (media.piefed.social)
๐Ÿ‘ 2
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] 18 points 17 hours ago (8 children)
  • [โ€“] 13 points 17 hours ago (7 children)

    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.

  • source
  • parent
  • hideshow 7 child comments
  • [โ€“] 10 points 16 hours ago* (last edited 9 hours ago) (3 children)

    Isn't VB.Net just .Net with weird syntax for the loops and ifs?

  • source
  • parent
  • hideshow 3 child comments
  • [โ€“] 8 points 16 hours ago* (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] 3 points 8 hours ago (1 child)

    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...

  • source
  • parent
  • hideshow 1 child comment
  • [โ€“] 2 points 4 hours ago

    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

  • source
  • parent
  • load more comments (-1 replies)