• NegativeInf@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    9 months 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
      link
      fedilink
      arrow-up
      5
      ·
      9 months 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.

    • Zangoose@lemmy.one
      link
      fedilink
      arrow-up
      5
      ·
      9 months ago

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

    • Kogasa@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      Not an intern, but this week I’ve unraveled some mysteries in ASP.NET MVC 5 (framework 4.8). Poked around the internals for a while, figured out how they work, and built some anti-spaghetti helpers to unravel a nested heap of intermingled C#, JavaScript, and handlebars that made my IDE puke. I emulated the Framework’s design to add a Handlebars templating system that meshes with the MVC model binding, e.g.

      @using (var obj = Html.HandlebarsTemplateFor(m => m.MyObject))
      {
        Name: obj.TemplateFor(o => o.Name)
      }
      

      and some more shit to implement variable-length collection editors. I just wish I could show all this to someone in 2008 who might actually find it useful.

    • Lmaydev@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      7 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.