I improved EF Core support by adding support for nullable primitive types and String<Tag>, which I plain ol' forgot. EF Core usage is hard to justify, because queries against tagged primitive members, e.g. Long<Blog> Id, have to run locally instead of on the client. The EF Core docs briefly mention it.
If anyone knows how to add EF Core SQL support for a type, let me know, please.
The Primitive types added ASP.Net Core support via thin wrapper classes that contain the underlying strongly typed primitive. They're wrapped because ASP.Net Core doesn't allow user-defined structs to be controller route parameters. My hunch is it's because you can't have a user-defined default constructor for the generic code to call, but I haven't even Googled this yet.
I changed the Scarp.Result namespace to Scarp.Results because client code had to type Result.Result.Ok("all is well") because the namespace and class have the same name (for client code that isn't in a .Result. namespace itself).
https://github.com/ryancerium/scarp
https://www.nuget.org/packages/Scarp/
https://www.nuget.org/packages/Scarp.AspNetCore/
https://www.nuget.org/packages/Scarp.EntityFrameworkCore/