TBH aspnet core has been the most stable web framework I've worked in my life. If you have good test coverage, upgrading projects between major versions often takes minutes — because nothing, or almost nothing, gets broken. Some things might get deprecated, but the old way keeps working for years, you can chip away at it slowly over the next year or two.

You still need to make sure that everything works, but that's what tests are for, and this has to be checked regardless of your tech stack.

Of course, they had a massive backwards compat break when moving from the regular aspnet to aspnet core, here's hoping nothing like that happens in the next 10-15 years..

▲ bob1029 2 days ago | parent | next [-]

I've hedged the stability risk by using the narrowest possible slice of the framework.

With enough experience you can accomplish pretty much everything using just the minimal API and router. HttpContext is the heart of AspNetCore. If you can get your hands on instances of it within the appropriate application context, you can do anything you need to. Everything else is dependent upon this. The chances that HttpContext can be screwed with are very, very low. There are billions of dollars riding on the fact that this type & API remains stable for the next decade+.

▲ jtbaker 2 days ago | parent [-]

do you still use the framework's DI pattern with this approach? I have an older school .NET app I work on (still Core) sometimes and haven't gotten much experience with the minimal APIs, although it looks attractive as someone that prefers lower level routers.

	▲	bob1029 2 days ago \| parent [-]
		I use the AddService() method to inject a things on occasion but its not used heavily. For lightweight apps I'll spin up things like a shared SQLiteConnection and inject it for all resources to use. The DI pattern is simple & clean at this scale. In my top-level program I define my routes like: `app.Map("/", Home.HandleRequest); app.Map("/login", Login.HandleRequest); app.Map("/account/new", NewAccount.HandleRequest); app.Map("/{owner}", OwnerHome.HandleRequest);` And then I have HandleRequest implementations like: `static async Task HandleRequest(HttpContext context, SQLiteConnection sql) static async Task HandleRequest(HttpContext context, SQLiteConnection sql, string owner) etc...` The actual HandleRequest() method can do anything, including concerns like directly accepting and handling web socket connections.

▲ tracker1 2 days ago | parent | prev | next [-]

I saw a lot of breaks between .Net Core 1, 2 and 3... since 3 it's been much more steady though.

▲ Varelion 2 days ago | parent | prev [-]

Or hope that key figures, or significant portions of the team don't get laid off. I don't trust Google or Microsoft products for this reason alone.

	▲	giancarlostoro 2 days ago \| parent [-]
		.NET has been powering StackOverflow for decades. All of .NET itself is MIT Licensed.