11 engineers on Hacker News describe using ASP.NET Core first-hand: 6 endorse it, 0 regret it, 0 are mixed.
“we moved to Core around 2.0 and never looked back, as an ecosystem it is so much better.”
endorse · production · ninjaoxygen · 2025-10-15 · source ↗ · wrong label?“We run multiple of these at a time and have no problems.”
endorse · production · noworriesnate · 2024-08-31 · source ↗ · wrong label?“The stack is ASP.NET Core with .NET 6 on the backend... I'm loving it, feeling very productive”
endorse · personal · romanhn · 2022-06-01 · source ↗ · wrong label?“It's mature enough now to be able to convert our (chatbot framework) solution from .NET Framework to .NET Core.”
endorse · production · woutercx · 2018-12-24 · source ↗ · wrong label?“I also use asp.net core both for personal project and company product. It works great especially with f# and giraffe.”
endorse · production · slaveoftime · 2018-12-19 · source ↗ · wrong label?“I'm refactoring it to ASP.NET Core on Service Fabric. Getting about 50x better real-world performance.”
endorse · production · xorxornop · 2016-11-17 · source ↗ · wrong label?“I was on a team using Vue.js for the frontend and ASP.NET Core for the backend.”
neutral · production · sebastianbk · 2023-11-21 · source ↗ · wrong label?“for an ASP.NET Core Project with the default pattern (i.e. with EF Core).”
neutral · production · ComputerGuru · 2023-04-23 · source ↗ · wrong label?“ASP.NET CORE( - Primarily ASP.NET Razor Pages for the web app.”
neutral · production · haacked · 2022-07-25 · source ↗ · wrong label?“based upon the exact same primitives as our main application (AspNetCore)”
neutral · production · bob1029 · 2020-12-21 · source ↗ · wrong label?“Right now I'm working with get ASP.NET apps into containers, by first getting them ported to ASP.NET Core and then into Linux containers.”
neutral · production · filleokus · 2020-07-01 · source ↗ · wrong label?