At least Entity framework is included in Umbraco since 12(.4?). And all my custom database stuffs are done with Entity Framework, so that works fine To be honest, I thought they were already done phasing out NPoco, but I guess I was wrong…
I think requirement to use MSSQL (except sqlite) is holding Umbraco to grow as real replacement for every other CMS even Wordpress. When people realize that they can use Umbraco on almost every cheap VPS with 2GB RAM then popularity might explode. I have some docker installations with MSSQL express but it’s always not ideal. Many times I just decided to use SQLite even on production, because it’s easier.
As noted above, it is not on the roadmap, so it’s not far along. Unfortunately it is not possible to help in this case, it’s a bigger project that first needs to be scoped out by HQ before we can move further on it.
So, don’t hold your breath, it’s going to take a while
This is probably true. We use and enjoy Umbraco despite MSSQL, not because of it.
Coming from a PHP background and enjoying easy setups, MSSQL for me has been the antithesis of simple database management. Onboarding new developers to the stack begins with apologizing for the complexity it brings.
Microsoft has sunset Azure SQL Edge, ARM64 support has been pulled quite some time ago.
Official Umbraco documentation explains custom table creation with EF for your own plugins.
How long until Umbraco will finally put EF (and database-agnostic storage) as a top priority? Or at least making it database-agnostic, since nPoco has multiple database providers.
The problem with the support for only MSSQL is that it is not FOSS, and Sqlite doesn’t really count since it performs so badly, plus it is not recommended to be used in production environments anyway.