The next step up from this is to combine this with webapi odata, that way the framework generated this sort of linq expression for you from a URL.
The irony here is the discovery .net core 3 and the EF core libs that make this possible are right now in a worse state than the ef6 and .net 4.x stuff regular .net people just migrated from.
Give it a couple years though and this will be special under .net 5 when you start notice it's literally write once, run anywhere.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The next step up from this is to combine this with webapi odata, that way the framework generated this sort of linq expression for you from a URL.
The irony here is the discovery .net core 3 and the EF core libs that make this possible are right now in a worse state than the ef6 and .net 4.x stuff regular .net people just migrated from.
Give it a couple years though and this will be special under .net 5 when you start notice it's literally write once, run anywhere.