Entity Framework Best Practices - Should EFCore Be Your Data Access of Choice? 

"If the way someone develops a C# application makes you angry, I suggest you reevaluate your priorities in life." LOL legend

Man, there are hundreds of videos on “how to EF”, and that’s fine. But your walkthrough here that included not only that, but also the pitfalls, what could cause problems, and WHY those can be problems was extremely helpful. The section explaining the string fields like NVARCHAR(MAX) was very informative and helpful.

Hey Tim, thanks for another great video! I've been learning a lot in your tutorials and it's impressive to see how deeply you understand the language and how clearly you explain it. Thanks for sharing!

Mr.Tim Corey, your courses are superb educational and great resources for learners of all expertise levels.

Where was this tutorial when I was trying to learn EF so many years ago. Really well made and I love how you show the simple things that are so often missed like where the PackageManager Console is in Visual Studio. I'll be watching a lot more of these videos, keep up the great work.

Just passing by to say: THANK YOU TIM! Your videos are awesome and are really helping to move towards a dev career, what you do for the community has granted you a place in heaven. Keep up with such amazing work, cheers!

If all of your other videos are this detailed, I'm going to watch your entire library. I was expecting to to see a couple instances of how to do something in Entity, but this video was so much more valuable then that.

I watched this video with great interest, and I have some comments to make. I have used Entity Framework fairly extensively since EF 4, up until EF Core 2.x. I didn't get a chance to use EF Core 3.x in production, as I retired three months ago. That should give you an indication of my frame of reference as it relates to EF. Anything I see here is, of course, the way *I* worked, and I'm not claiming my way was the best - only that it well worked for me, and in some cases reduces or eliminates some of the areas that you pointed to as causing you some concern. First, I would never allow any data access tool, EF or otherwise, to create the database for me. Though I wasn't a DBA per se, I created multiple databases for use with my applications, and I always created those databases manually in SSMS. Not only did that allow me to define the tables and columns in exactly the way I wanted (for example, I didn't need to know or care whether EF (or nHibernate, etc.) pluralized table names), but I could also create secondary indexes in the "normal" way in SSMS, without needing to learn anything about how EF data annotations (or fluent API) worked for defining indexes and so on. I just think it's better to have complete control over the database structure. The only thing I ever used data annotations for was for required or max length, which allowed the UI to perform validation of data via Validator.ValidateObject(), et al. You showed the long sp_executesql query generated by EF. I actually never encountered that, as that's something new in EF Core 3.x. In EF "Classic" and EF Core 2.x, one insert statement was sent to the database per row insert (and all the inserts were performed in a transaction). It's interesting to note that the EF team got crucified for that approach, as it caused numerous INSERT statements to be sent to SQL Server when bulk inserting. I myself encountered more than one occasion where I saw an order of magnitude or better performance increase when I used EF addons such as EFCore.BulkExtensions and the like, in the few cases where I needed to insert many rows into the database at once. Now that the EF team wrapped the multiple inserts into a single statement, they're again facing criticism. I'm not any kind of security expert, so perhaps there's a better way they could have reached the same end goal, but definitely sending a single SQL statement per inserted row wasn't being happily accepted. I personally never used migrations, as I found them to be too limiting (at least, when I looked at them; it's possible they gained functionality later on). I found that in many cases when I made a database schema change, I needed to do some serious work on the data. For example, I might factor out three columns from one table and two columns from another table and put them into a new table, referenced by both of the original tables. That kind of work didn't lend itself to migrations, so I wrote a little "framework" for database updates, and then whenever I had occasion to update the database, I filled in the guts of the framework with the handcrafted SQL statements that I needed. So I didn't use EF at all for database migrations. I wrote desktop applications, and I was able to completely encapsulate EF into a .NET Standard 2.0 class library, with no reference whatsoever from the UI project(s). This might be different for me because I didn't write web apps (though I'm assuming this would work equally well for a web app), but I got the (encrypted) server name, database name, user id, and password from a local config file, and then passed those to a static method in the data access library, which cached the information. I wrote a UnitOfWork class that encapsulated the DBContext, and the application made calls to UnitOfWork. The UnitOfWork class instantiated the DBContext, using the cached connection information. The main application never knew it was using Entity Framework at all. Finally, I don't think the query where you loaded all people, addresses, and email addresses was a fair one. You wouldn't load them like in reality that unless you planned to do a bunch of updates to all the data and then resave it. Instead, you'd use DTOs and you'd have a projection query, the same as I imagine you'd do when using a different ORM, or when issuing direct SQL statements. I have, though, on occasion done the same thing in EF Core (2.x) that you said you do in Dapper, which is to issue two or more SQL statements independently, and then merge the resulting data using C#. I understand what you're saying about needing to learn EF before using it, but I would argue that that can be said about literally any technology. I wouldn't want to sit down and try to write an application using Dapper (I've never used Dapper before) without studying it fairly extensively. I wouldn't allow Dapper to automatically create the database, just as I wouldn't allow EF, nHibernate, or anything else to create it. So I think that you're being a little bit hard on EF, as it's an incredible data access technology. In my opinion, the types of "gotchas" that you point out relate to any technology, including direct SQL / ADO.NET. I can easily write a horribly performing, though straightforward, query, in direct SQL. For example, I've seen tons of examples that show "SELECT * FROM Customers", which you wouldn't (hopefully) ever do in real life.

Thank you Tim Corey. It's a great chance for us to learn from your courses. For checking if there is any record in table, Any() functions should be used for better performance. Count() has to read the whole collection of the table but Any() immediately returns after reading a single record.

i am currently using this video as a go to guide whenever a friend of mine mentions using EFCore. Thank you Tim, you really are awesome !

I am SO excited to see you finally covering this topic!

Your lessons are pure gold Mr. Corey! Some things you said I learned the hard way via trial and error myself but other things you advised can’t be underestimated. Such a good advices you are giving to us! You even know about War and Peace book and it tells us as to how knowledgeable and intelligent you are. I am amazed by your charming personality Tim! Thank you so much!

This video is so detailed and thorough it shouldn't even be free

Love this. Been making similar arguments for project development for a few years. This is just explained so clearly where now I can just send a link! Good man yourself

Amazing video. I'm pretty new to EFC and total newbie with SQL. I learned a lot from this video, and it made me realize that I should in fact invest more time to learn what I'm working with. Thank you!

Really well made and I love how you show the simple things that are so often missed.

Man! your videos always have fully explained satisfying answers to my questions. Keep up the good work

You are the best programming teacher I've ever met. Thank you so much for this content.

These videos are great! I just like to have them running so I can pick up on all the tidbits you mention. Great stuff!

Looking forward to watch this video. One of the confusing subject I have faced with seemingly no escape route.

I agree with everything your saying here in regards to having to be experienced in order to use EF efficiently. However, everything you laid out is from a "code-first" perspective. I use EF in all my projects, but I don't use their migration and schema tooling. I use good-ole fashioned DB-first approach. I use SSMS as much as I use Visual Studio. Also, I only use EF for entity level CRUD operations and very basic queries. If I have ANY more-than-basic queries or data logic, I use SPs, Views, Functions, etc. - then I call those functions through EF. I wouldn't recommend using EF for a code-first approach, either. However, I wouldn't recommend code-first AT ALL. Personally, I despise the code-first approach - but I also appreciate the fact that it works for other people.

Thank you for all your excellent tutorials! One side note I would like to make if I may. The EF design tools can be installed in the EFDataAccessLayer class project. After you install the tools in the class project, make this project as startup project from Visual Studio solution, run your migrations from PM> and switch startup project to UI project when you want to run the application.

Your content and delivery is simply great.. and easy to understand. Thank you so much for the wonderful tutorials.

What I love about this video is that you explain each topic with the right level of detail and in a succint and informative manner. Even someone who has primarly used Dapper loved the content and learned a lot.

Thank you for this great tutorial. Cleared a lots of doubts I had.

I feel like it's still important to learn it for people who are planning to get into professional industry. EF is widely used in many companies ranging from small to large, I honestly I have heard of dapper until I came across your channel. The best way to learn is to use the frameworks, if you consistently avoid well-known frameworks you won't really grow as a developer and limit yourself in the professional world.

The first long video on youtube I watched from beginning to end. Worth every minute. Thank you for your hard work, smooth voice, and deep knowledge!

While I didn't know about this channel, when I was trying to write migrations from other channels, no one went that deep, they didn't show the errors, and so I had a problem every time I found a problem myself. in the end, I lost my enthusiasm and instead of writing with migration, I switched to writing db first. when I discovered this channel, everything was great. Thanks

Tim, you did an great job covering this topic. I try to tell people that programming is the last thing that you do. And your videos demonstrate this. You have to know exactly what you're doing or pay the price on the backend. Awesome video!

I knew everything you said. But still good to know, that there are such a good tutorial for people who interested in what they are doing. Good job.

Hey Tim, your content not only helped me to understand code and program, but also helped me to see the problems in a completely simple way. Your way of teaching and talking out the solution is unique & simple. Thanks for that.😀

The reason I find Tim's channel so useful is because he always explains why we do certain things one way and not the other and not just because he said so!

I consider myself a pretty experienced EF developer, but had only just learnt about the drawback of using Includes from this video. I had assumed it did something along the lines of QueryMultiple in Dapper. Just shows it's always worth looking at videos on topics you consider yourself well versed in. One thing I was waiting for you to bring up was projections. Using Select statements is an extremely important part of making sure that EF runs smoothly for me. It solves the issue of Include, and removes the change tracking which is another big cause of slowdowns. Using projections you can get near identical performance to Dapper, while also keeping all the benefits of EF core. One of the most important things for me is the compile time safety of my queries. Admittedly I haven't watched your videos on how you use Dapper yet so I'm not sure if you've addressed this. I also think using the right tool for the job is an important aspect. If a query is complex and needs to be hand crafted for performance, writing the SQL manually and using dapper is the better option. If you just want to pull a few fields from a table or two and put it into a VM/DTO, I think EF with projections is usually better. I'm not against using both in the same project and using EF for 90% of my needs, and Dapper for the last 10% of more tricky/important aspects of the application. Lastly, in case you didn't know, you should be able to change the 'Logging.LogLevel.Microsoft' in the appsetting.json to be 'Information' and all the queries run by EF core will be logged to the ASP.net console. I find it much easier to look at the queries as they go through there than trying to filter through the junk in SQL Management Studio. Just my 2 cents, great informational video overall, especially for newer developers!

Hey Tim, great tutorial. I enjoyed the details on where entity framework falls short -- they actually gave a great insight to how this system operates behind the scenes. I would like to propose a suggestion for a tutorial as to how would you implement a repository/unit of work patter on top of entity framework. Thank you for all your hard work. Subscribed

Thanks Tim! I wish I had this a couple years ago to share with my junior developers. I have had the same reservations as you for many years about ORMs in general. I have seen them totally derail an application once it hit production. My team used EF for the first time a couple years ago and I have been fairly happy with it, but this video pretty much sums up my feelings about it. As a hiring manager, it has been a challenge to find newer developers that can work "without the net" of an ORM. I believe that knowing how to do both is critical to being an experienced developer.

I've been looking a lot of ef guides. I also have prior experience with it but never created a project from scratch myself, this guide is absolutely the best one I've found so far. Superb job and the flow you have is absolutelt great! Thanks a lot you saved me a lot of research time

Small correction: Ascii has 256 characters Unicode has 143,859 characters Thank you Tim for your hardwork in putting these videos together. Greatly appreciated 🙏

Hummmm, in my whole development life this is the first time to see this type amazing explanation. Great job.

Thanks a ton, Tim. I loved the way you showcased the little things we always miss.

This was really helpful for me TIm. I really appreciate the careful and balanced presentation on the topic. I'm an experienced SQL developer, but brand new to EF and C#. Many of the topics in this video were eye opening for me. I'm not sure if I'll have the ability to use Dapper on this client project, but you helped me at least be well aware of some of the biggest pitfalls to avoid.

You dont find these best practices and tips from other videos... They just teach you how to write code... That explanation and difference on approved age in the where clause is bravo!👏👏👍👍

Not sure if this has been addressed in comments already, but for your first issue about having to reference EntityFrameworkCore from the web app in order to call services.AddDbContext, you can simply reverse the dependency. I use a static method on my Context partial class that takes the IServiceCollection as a parameter. This allowed me to remove the reference to EntityFramework from my web app project all together.

A video of this quality is rare - thank you so much for this. I also learnt a lot from it. Well constructed and very clear. Thanks for covering some of the pitfalls and nuances. :)

Thank you So much Tim. Everything is well explained and clear all throughout! More videos like these please!

Awesome video! Thank you for making this one. I like EF very much. It hides the database mechanics once you have set it up correctly but when you get a problem later on, good luck with that. Great teachings coming from you about EF, I love it!

Simple, clear, easy to follow lesson on this important topic.

Dude your tutorials and calm and collected explanations are top notch. For real if you like this youtube thing, don't give up on it. You make excellent videos!

Thank you!! Ton of information in a single video. You highlighting multiple times about issues in production hit the chord with me. Hope you have/do some videos on memory leakage and exception handling.

you can use Iqueryable method for where clause, like predicatebuilder that is functional and also it is easy to use

This One lecture is better then my half semester in uni. Thank you so much for your kind effort ❤️ Love from #Pakistan

Thanks Tim for this nice video, we are already using EF Core in production and in the beginning we got some performance issue but now we have optimized the LINQ query.

Tim - Great video!! I've never really used EF primarily because it seemed more prudent to separate UI. models and the underlying storage. Your video confirmed that decision. I tend to lean on using SPs for nearly 100% of DB access using parameterized SPs and SQL. There is something comforting about being able to change an SP to impact performance and results without having to rebuild and re-deploy code. .. Thanks!!

Hi, Tim. I'm wondering if you've been keeping tabs on the development of EF Core. If so, do you feel they have made any significant improvements since you produced this video that would address any of your core concerns? Or, do you feel that any progress has been made in other areas that could help to offset any of your concerns?

16:58 You can put in an override for OnConfiguring in the PeopleContext class protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder) { base.OnConfiguring(optionsBuilder); optionsBuilder.UseSqlServer(Configuration["ConntectionStrings:YourConnection"]); } Therefore your front end no longer knows about entity in this circumstance.

That was amazing, Tim. Thank you very much for all the work you have to put this explanation up.

Wow, this is an amazing video! We were taught to use EntityFramework Core at my university, but they did not mention ANY of these huge drawbacks and how to overcome them.

Hi Tim, we are selling a white labeling product for many clients, each one of them has a totally different application & database version. One of the major benefits that we have in EF, as you said the tooling is great in EF, so we are using it to manage Migrations and to generate it, also we integrated that with our CI/CD so all DBs automatically using the same tooling. What is the better alternative here? What about doing CQRS and using EF for write operations at least to make things faster in development. And thank you for the great video.

As of EF Core 5.0, Split Queries have been introduced to solve the cartesian explosion problem that was described in this video. This feature significantly improves single query performance, and I was happy to see it! Granted this does not solve the fundamental problem that by default, it's easy for a newbie dev to get into trouble, which is your point. Especially when I tell you Split Queries, which can be enabled globally, is by default turned off! But nevertheless, for those of us that are experienced and read documentation, EF is now extremely viable.

Dear Tim! I've got a new job, thanks to Your videos! Keep up the good work!

Tim Corey DOMINATES this market. The best quality videos. The most understandable videos. An absolute asset to YTs education sector.

This is exactly how I felt about EF. It’s analogous to a piano, press all the white keys, ooh this is easy but… The slickness of the tooling doesn’t give the developer enough of a heads up toward the power it wields under the hood and only an advanced developer would be able to infer/reverse engineer it from an inherent understanding of SQL server / db design.

To be honest EF most of the time is fast enough. Emphasis on the enough and not the fast. We have a fairly large system backed up by EF6 and users never mentionted anything about poor performance but to be fair we made precautions and optimised the performance heavier parts. For us the faster development outweights the performance penalty which is not a real issue (at least for us).

The best tutorial about EF I have ever seen😍🔥🔥🔥🔥🔥 thanks Tim

Geat video, thank you tim for taking the time to make these!

I'm watching this video as a long time user of Entity Framework (before EFCore was a thing) and as someone who successfully uses Entity Framework Core on enterprise applications that has a lot of data. I wanted to bring up a quick note though of you talking about that you "hate" how EF could technically expose your DB Credentials if you developed it on a desktop application. While that is true, I could make that argument for any desktop application that connects directly to a database. You even mentioned it in the video, that the user technically owns that one part. Any desktop application that connects directly to a database will have to somehow put username and password on the users system. Be it encrypted (and you said it, user technically owns one part of that key) and compiled into the code, it's still possible for me to mess around find it. While there are pros and cons I myself would most of the time develop a desktop application to talk to a mediator, like some kind of web API. I can manage access easier that way and can manage what is actually going in and out of my database. I could even develop some type of cache before it gets to the database, but that is whole different topic. So for most systems I end up building some mediator to talk to a desktop application, unless I am building like an offline only application. Then at that point if the user wants to "hack around" on the local db it talks to then go right ahead. So for me I guess I just don't think it's fair to just really talk about EF there. I feel any desktop application that connects directly to some remote database can have that issue, no matter what you are really using at the data access layer.

I find that data annotations are essential for getting more control on creating a model and they are easy to understand

Hey Tim, i would like to thank you personally because you have done great video work...I really understand everything that you explain in video. I have just started a few months ago a coding bootcamp and your videos are extremely helpful. Well done. I wish you everything best!!!!

That's incredible, thank you so much to tell these darkest part of entity framework this information help me to understand that nothing is perfect you do have to go in deep to find out how the things really working.

I like EF Core, much more than EF 6. Version 3.1 is a great improvement, just waiting for the documentation guys to catch up since the docs are still on 3.0. I think because MS is so invested in it, it has a large community and support, which is a big plus.

1:14:30 instead of .Count() == 0 it's better use .Any().

Tim, thanks for the videos, keeping them short and direct to one aspect at a time. Especially the initial going with the established connection to the database getting all else started in place. I have been doing the hard grunt work of CRUD with parameterized SQL commands but thought I might as well try to learn new (even though near retirement and not a big deal, just like to learn). I do see the much lighter implementation than SqlCommand, SqlParameters, SqlConnection and building out queries, but much of what I do also deals with dynamically prepared and filterable queries for getting data and just know that it COULD be done, just not changing over existing work, just looking to the future. I also notice you doing hard-reference object names to get to the form's objects and such. However, do you also have experience using MVVM patterns and bindings such as text to a property object instance. I find that approach works nicely in that you dont have to know what the controls are on the form, you just look at the model's properties to act on for values. You dont have to care about what the forms object name is to get them. And if some values are numeric based, and bound to a textbox control, you dont have to think about a valid value as anything invalid as number is just zero. Just a comment though would be an additional level of confusion to those try trying to understand the basic flow operation you have provided so well and completely get the point across. Enjoyed all the videos.

Brilliant tutorial!!! This should be a standard tute for anyone starting out in development with netcore etc.

Just discovered your channel. I like that for this topic you got right into using SQL profiler to see what EF is doing. Learning how to make EF do something close to what you would write by hand is a key ability to pick up, DDL and DML both. You do a good job of giving people the info they need to start down that road. As commented EF gives you many ways to shoot off your toes but people can also write some pretty scary SQL queries out of ignorance as well. Loading child collections manually is pretty easy, I rarely use .Include directly.

Thank you for this excellent tutorial. Best video I have ever watched on EF.

Awesome tutorial. I don’t even want to call it a tutorial, more like training or a small boot camp on EF Core . Thanks Tim!

It's really a great video for a beginner who wants to refactor the existing application from any other platform to C# and EFCore. Thank you, Corey!

This is a fantastic video. The number one anxiety point of moving our legacy applications to a web app has been my understanding that I literally knew enough about Entity Framework to be dangerous. The mere thought of applying database migrations as the project progressed into production with continued development was terrifying. You've provided much of the information I need to navigate that particular mine field. You've also got me considering Dapper, instead.

Damn, its rare to find a creator who actually cares. Thank you :)

You just mega reinforced my belief in stored procedures & lighter weight ORMs. Thanks!

Hey Tim, thanks for another great video! I've been learning a lot from these. The main point which I want to mention is, you just explain each question before I think I need to ask :) and it's impressive to see how clearly you explain it. Thanks for sharing! Your dedicated student :) :)

went through the whole video and do along with it. I'm deciding whether use Dapper or EF Core in this moment, the deep analysis made a long video never felt long, all information is really valuable. thank you!

Hi Tim, thank you for the great video! Every minute is worth watching!

Just finished your long video. Very helpful!

The fact that is 2.5 hrs tutorial and for FREE on youtube is ming boggling. Most people share knowledge in general. Thankyou so much Tim.

Thanks for the video Tim. We use Entity Framework a lot in our in house software, work in an internal software dev team. I'm still new to C#, .NET, come mostly from a Front end, JS development so this has helped me to understand that EF is not as simple as it appears with the hidden dangers. I still need to use it as that's what our projects are running but this has helped me to take it a bit slower and really think about what I'm doing. Thanks!

Hi Tim, First of all thank you for this video and for all videos posted on your channel. All very reliable content. I watched your video because I asked a company to rewrite for Windows platform an old application I inherited. They came back with a windows forms, C# and EF solution. I am now in charge of the maintenance of the application and as DB designer and with very good knowledge of SQL I am always skeptical with all these frameworks. In past life I was also maintaining a Java/hibernate web site. I must admit that EF seems to generate a correct SQL query than hibernate 5 years ago ( perhaps it has improve since then). To be noted that the database is well normalized, not fully obviously. So as a DB manager I am sometime frustrated by the fact that I could have wrote a better more efficient query than EF. But EF and mapping tool are quite good in facilitating integrating between code and dB. Nevertheless in my case I have to customize and add some specific features in the EF part to manage update of object as well as other trigger in backend to ensure that my data are correct and can be exchanged. And this aspect is quite a nightmare from now. Perhaps for editing data is better to use classical DB direct Access and for viewing DB data to rely on EF for faster development. Anyway thank you for sharing your knowledge. Max

Hi Tim, thanks for the video! I don't like the code first approach just the same reason you demoed in the video. So in our projects, we use db first. And we do the revision control though the scripts, similar like flyway. I am glad that we avoided most of the pitfalls in the video. I think the benefit of EFCore is that after you knowing how EFCore works (although you might spend some time to learn), it's quite productive, and since it's ORM, it can keep the code base quite clean (again, we don't use code first:) this is important). Although dapper also has things like simpleCRUD, but you need do more stuff when handling for example, many to many scenario. In conclusion, learn EFCore well then it will be quite benefit. Thanks!

Thank you for this video Tim. I wish I had seen it earlier as you mentioned some great points. EF is (too) good at hiding what does and does not get translated to SQL, even when there are huge performance implications.

Hi Tim ! Thanks for share part of your knowledge with us, it's been a pleasure to apply my free time learning with your videos! Just a suggestions: Maybe it would be nice if in the videos' descriptions have some kind of summary about in what time in the video that topic will be discussed.. anyway just a suggestion, thanks a lot for your work!

Your's course not only explains how to build a program in Visual Studio but also is a great lesson of how to speak in english. Big thanks.

Thank you for this tutorial... its easier than I thought. Also thank you for showing us the "dark" side of EF. I will watch out when doing my queries. In the worst case I will just write a SQL query. Tbh I even prefer writing them instead of figuring out how EF creates them... but for quick and small stuff I think its fine.

Very thorough!! Thanks, Tim!! Lots of good information for data access in general. I also learned some new debugging techniques! I didn't know you can pin values in the Locals window - pretty cool!

I understand what you mean at @15:30 about feeling weird with the Web project knowing about EntityFramework. The way I solve this is by creating a extension method in the DataAccess project (we'll call it .AddDataAccess(this IServiceCollection services) ), and then inside of this method I wire-up the .AddDbContext(). Finally, in the web project, you can simply call services.AddDataAccess() inside of the ConfigureServices, and the web project doesn't need to know anything about EntityFramework. Works great. Thanks for all of your videos!

Thanks a lot! I've watched the whole video and there is one thing I would like to mention. I am a EF user (haven't used Dapper) and you talked about optimalisation. In the part where you showed the `Include` and what the differences where you forgot to mention repositories. You went in to quite some detail on optimalisation in data storage, and memory usage for queries. But without repositories who will handle getting data efficiently it is fair to say that EF is not optimal for production. Of course we could populate the lists manually in C# without using the Include, but this would be ~10 lines of code everywhere in our application where we wanted to get people. So that is why explaining repositories in a "best practices" guide would be fair. English is not my primary language so it might come off a little bit negative, which is not what I'm trying to enforce here :D Thanks for the explanation I learned some new things!

Thanks @IAmTimCorey, this is great. I have a lot of experience with other languages but now need to use C#/.Net and EntityFramework for an upcoming project and this video has been awesome. Because of the amount of experience I have with Hibernate/JPA and ORMs in other languages it's relatively easy to pick up but you're pointing out some very interesting details here which are easily overlooked. Very much appreciated, your material will get a strong recommendation from me!

I use EF to build the Tables and do Insert, Update and Delete, but then I use Dapper for advanced SQL queries, it has been a blast so far!

Hi Tim, thank you for great job towards C#. I was thinking that this language is losing market ground. But now with your detailed videos I changed my mind and came back. Thank you again.

As someone who is learning c# for work and who is generally framework averse because of just how much they typically do for you, thanks for the excruciating detail. very very helpful

I loved the way you get to the detailed explanations!

Superb overview of Entity Framework best practices, Tim. I'm intrigued by Dapper.