Yes, please make a follow up and dig deeper into those two compilation-boxes!
@VladimirRomanovsky-Errdonald Жыл бұрын
Starts at 2:36
@maksadTohBhoolChuka Жыл бұрын
Thnx
@philipstuyck269411 ай бұрын
In our company we have a legacy system that was created even before EF. Now I added a feature that allows linq for filtering which transforms the linq predicate expression into the filter that our legacy system recognizes. But that legacy system must at a certain point create SQL too, and materialize too, but then to our own classes. It does have change tracking, but does not have the notion of a context, that is hidden to the users, nor does it have a unit of work. But I was thinking that instead of writing my own visitor to create our legacy filters, i could get the SQL from the provider by perhaps adding some attributes or fluent api and fake context objects in our code. Ideally without changing any code in the provider. Because then with an update of the provider, I don't have the problem of code merging. But even if I have to dig through the provider code and use a subset of it, it would still be cool, because the quality of the sql generation is very likely very good.
@ramashankar2750 Жыл бұрын
As shay outlines , Index based in memory datawell using LINQ and DI service is what we use to maintain State on WASM across pages to overcome cascading values issues e.g An Invoice which consists of 20 entities (nested interfaces) and with entity splitting.
@MeNourovic Жыл бұрын
thank you for the video.
@Andy01010 Жыл бұрын
In all honesty, you need proper guidance videos similar to this one in the documentation section on how internals work when a new version of EF is released.
@amrosamy8232 Жыл бұрын
we can say the expression is a func that is written in a single line of code without surrounding it with curly braces
@MohammadElmi Жыл бұрын
and it has a #beginner tag :))
@maksadTohBhoolChuka Жыл бұрын
Is it not beginner friendly ?
@Roshan-tb3iz Жыл бұрын
That's a valid point @MohammadElmi. You need to be maybe an intermediate developer and have at least some experience programming EF Core by using a DbSet class to understand this video. It's about internals of EF Core and not an introduction to the topic.