1631

dotnet developer (programming.dev)

submitted 9 months ago by JPDev@programming.dev to c/programmer_humor@programming.dev

123 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] dan@upvote.au 10 points 9 months ago* (last edited 9 months 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.

[-] NegativeInf@lemmy.world 7 points 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 5 points 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 5 points 9 months ago

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

[-] neutron@thelemmy.club 2 points 9 months ago

I am so sorry, man. No one deserves this.

[-] kogasa@programming.dev 2 points 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.