3 ms·

I've seen a number of startups who are stuck on .NET Framework, simply because some affordable agency built them an MVP with ASP.NET a while ago and it worked (

by fhd2 2y ago

I've seen a number of startups who are stuck on .NET Framework, simply because some affordable agency built them an MVP with ASP.NET a while ago and it worked (TM) to get the business going. Then someone like me gets called into a situation where they have ridiculous hosting costs (Windows-only, typically also MS SQL), nasty performance issues, and struggle to stay productive and find developers. The most reasonable path forward I see in those situations is a gradual migration to .NET Core and something like PostgreSQL. And that's a major investment. Microsoft couldn't have made .NET Framework code harder to port to .NET Core if that had been their explicit goal. I find database migrations with Entity Framework similarly difficult compared to other ORMs. Startups can sometimes afford such investments, but often not. And that's how you ironically get 2-3 year old startups stuck on a death march old school enterprise code stack. It appears to be more common than I'd like it to be.

neonsunset 2y ago
This is completely self-inflicted. No one should be using obsolete stack, that's it. .NET (back then Core) has been going on for 9 years. Surely there was time to finally let .NET Framework choices die. (also a common theme on HN, to complain about problems that took place ages ago and imply they are still relevant)
adzm 2y ago
Really if someone can make something that allows legacy ASP.NET code to run on .net core, that would be huge for getting older projects migrated. For example, https://github.com/zzzprojects/EntityFramework-Classic https://github.com/zzzprojects/EntityFramework-Classic EntityFrameworkClassic is a fork of Entity Framework 6 which runs on .net core but still lets you use your existing EF6 code. ASP.NET is a much different beast though, but I don't see any technical reason that it would not be possible. I keep expecting one to show up. I think the ISAPI integration is the biggest hurdle there; lots of weird behaviors that would have to be addressed.

by fhd2 2y ago

neonsunset 2y ago

This is completely self-inflicted. No one should be using obsolete stack, that's it. .NET (back then Core) has been going on for 9 years. Surely there was time to finally let .NET Framework choices die. (also a common theme on HN, to complain about problems that took place ages ago and imply they are still relevant)

adzm 2y ago

Really if someone can make something that allows legacy ASP.NET code to run on .net core, that would be huge for getting older projects migrated. For example, https://github.com/zzzprojects/EntityFramework-Classic https://github.com/zzzprojects/EntityFramework-Classic EntityFrameworkClassic is a fork of Entity Framework 6 which runs on .net core but still lets you use your existing EF6 code. ASP.NET is a much different beast though, but I don't see any technical reason that it would not be possible. I keep expecting one to show up. I think the ISAPI integration is the biggest hurdle there; lots of weird behaviors that would have to be addressed.