Well, you can do that with LINQ + EF and embedded databases like SQL Lite or similar.
EF code-first is also on the right track, but the fluent and attribute mapping are awkward, foreign key associations often have to be unpacked directly as value type keys, there's no smooth transition between in-memory native types and durable types, and schema migration could be smoother.
Lots of the bits and pieces of what I'm describing are around but they aren't holistically combined.
https://learn.microsoft.com/en-us/dotnet/fsharp/language-ref...