C Sharp

1526 readers

5 users here now

A community about the C# programming language

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

Rules

Rule 1: Follow Lemmy rules
Rule 2: Be excellent to each other, no hostility towards users for any reason
Rule 3: No spam of tools/companies/advertisements

Related communities

c/dotnet

founded 1 year ago

MODERATORS

Ategon@programming.dev

nibblebit@programming.dev

Spyros@programming.dev

-11

.NET and C# are in trouble. Here is what I'd do. (www.youtube.com)

submitted 1 month ago by SmartmanApps@programming.dev to c/csharp@programming.dev

11 comments fedilink hide all child comments

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

[–] SmartmanApps@programming.dev 1 points 1 month ago (1 children)

Yes, that's his point. That if you've released your app close to the end of the period, then you're forced to upgrade your app right away, even just to keep getting security patches, on top of any bugs you might already be trying to get on top of with your newly released app. Other systems have a longer support period and you wouldn't be faced with that.

[–] Mihies@programming.dev 1 points 1 month ago

If you look at LTS dates, 6 overlaps 8 by a year. And when it comes to patches, there are two scenarios. One is framework dependant app where you don't have to do anything. And there is self-contained where you have to update the app - but how else would you patch it - this is the same for every app out there, isn't it?