Honestly, I always use the "database first" approach and generate code manually (I know there is a command-line utility but don't care about it). I really love EF Core and it made my development days soooo much easier. I would never use anything else. Very happy with it. Although, once you start working on complex queries, you are really better of doing stored procedures, as complex SQL Linq queries are PITA and very confusing.
Question. I have noticed today that I no longer need to use ‘ThenInclude’ for including objects from properties at multiple levels down. For example query.Include(x=>x.User.Address) works absolutely the same as query.Include(x=x.User).ThenInclude(u=>u.Address) If true this is so handy. Am I right or have I missed somthing?
Arthur said it right "EF Core is used to store your C# objects to a database". So many people think ORMs are for accessing databases from their programs. A small but very important distinction.
@@pedroferreira9234 There are a thousand ways to do everything. If he made a private set property, someone would have asked why not make it readonly. Sometimes it makes no difference at all; sometimes it's an important choice. For this tutorial... who cares.
![Getting Started with Entity Framework Core [1 of 5] | Entity Framework Core for Beginners](http://i.ytimg.com/vi/SryQxUeChMc/mqdefault.jpg)
Arthur knows his stuff
Honestly, I always use the "database first" approach and generate code manually (I know there is a command-line utility but don't care about it). I really love EF Core and it made my development days soooo much easier. I would never use anything else. Very happy with it. Although, once you start working on complex queries, you are really better of doing stored procedures, as complex SQL Linq queries are PITA and very confusing.
Question. I have noticed today that I no longer need to use ‘ThenInclude’ for including objects from properties at multiple levels down. For example query.Include(x=>x.User.Address) works absolutely the same as query.Include(x=x.User).ThenInclude(u=>u.Address)
If true this is so handy. Am I right or have I missed somthing?
The .ThenInclude() is to include a "many" relationship. Your User.Address is 1-1
@@sebastianfjastad7928 thanks!! Not sure how I missed that after a couple years of using efcore ☺️
EF Core team is raising the bar again!
Arthur said it right "EF Core is used to store your C# objects to a database". So many people think ORMs are for accessing databases from their programs. A small but very important distinction.
why not just use "private set;" doesn't that make it read only ?
That only means you can never set it outside of the class but if you have a public function inside the class that can set it
@@MAXMAFFIA2013 ik that, i just think if the main goal is to not change outside the class private set works the same way.
@@pedroferreira9234 There are a thousand ways to do everything. If he made a private set property, someone would have asked why not make it readonly. Sometimes it makes no difference at all; sometimes it's an important choice. For this tutorial... who cares.
Superb!
Nice seeing some C#9 stuff and F# crossover like the immutable stuff.
But that 'include' magic though... 😲
It would be good to get the new version to have a designer like the old ef did for new people it’s Easier to understand