• HeHoXa@lemmy.zip
    link
    fedilink
    arrow-up
    8
    ·
    11 hours ago

    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.

    • galmuth@feddit.uk
      link
      fedilink
      arrow-up
      1
      ·
      2 hours ago

      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…

      • HeHoXa@lemmy.zip
        link
        fedilink
        arrow-up
        6
        ·
        edit-2
        10 hours ago

        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.

        • teslekova@lemmy.ml
          link
          fedilink
          English
          arrow-up
          3
          ·
          8 hours ago

          As an Australian, I understand what happened. They were all drinking VB while coding it.

          • jobbies@lemmy.zip
            link
            fedilink
            arrow-up
            2
            ·
            4 hours ago

            Its not even that interesting. Working with Visual Basic is coding with all the fun sucked out of it.