• neutron@thelemmy.club
    0·
    1 year ago

    And then there’s .net classic and .net core. Making up two entirely separate names shouldn’t be difficult for marketing executives.

    • dan@upvote.au
      1·
      1 year ago

      .NET Core doesn’t exist any more. It’s just .NET now. I think that changed around the release of .NET 5?

      The classic version is mostly legacy at this point too.

      • neutron@thelemmy.club
        1·
        1 year ago

        My workplace insists on using dot net classic to recreate a twenty years old VB app that should be able to drink, vote, and drive.

        Please send help. SQL queries are a spaghetti mess and all the original devs are probably gone or dead.

      • NegativeInf@lemmy.world
        0·
        1 year ago

        Just because it’s no longer supported doesn’t mean there’s not some poor intern refactoring spaghetti backend in a basement somewhere using it.

        • dan@upvote.au
          2·
          1 year ago

          Sure, but you can still find plenty of info on it by searching for .NET Framework or .NET 4.6. All the documentation is still available. Its just not in the spotlight any more.

        • Lmaydev@programming.dev
          1·
          10 months ago

          It is very much still supported and will be for a very long time.

          You just shouldn’t start any new products using it.

        • Zangoose@lemmy.one
          0·
          1 year ago

          Hi, it’s me, the intern refactoring the spaghetti .NET core backend. I’m not in a basement though. AMA