ASP.NET Monsters #47: Julie Lerman and the State of EF Core

Play ASP.NET Monsters #47: Julie Lerman and the State of EF Core

The Discussion

  • User profile image
    stimms

    Great video, sorry I missed recording it!

  • User profile image
    Nicole Bletsky

    I just watched your video and was super impressed. I'm in the process of leading an ERP implementation and was wondering if the guy on the right...is his name David?...wondering if he'd be interested in joining our team in this business transformation. We could use an intelligent, good looking, self-motivated individual who is capable of thinking through complex business processes and be creative in implementing software to enable people to work more efficiently. Please contact me at the email above if interested.

  • User profile image
    David​Paquette

    @Nicole Bletsky: Our right or your right?

  • User profile image
    julielerman

    Surely Nicole was confused and meant me when she referred to a good looking, self-motivated individual,capable of thinking through complex business processes. Okay yes,I'm not a guy and I'm not on her right our our right but still ...

  • User profile image
    Simone​Invernizzi

    From the moment I started using async methods everywhere I never had any issue with lazy loading, never got that wrong not even 1 time.

  • User profile image
    julielerman

    @SimoneInvernizzi ... Lazy Loading is a great tool in the right hands! :)

  • User profile image
    Jon

    I'm a little tired of people constantly picking on lazy loading. Yes, you can get burned by it, but, you can get burned by any number of other problems when using an ORM. One example I've seen is where you do a projection and only query for a few properties across several tables that have lots of columns. I've seen it return all the columns in the SQL query. Another problem that I've seen that I think is a current bug is if you are doing a projection on tables that include left joins. It ignores Skip() and Take() and does it in memory. To me, it looks like the new "mixed client/server evaluation" is something new that people will get burned on. For example, if GroupBy() is currently evaluated on the client, that will result is horrid performance if you are working with a result set that is at all large. Also, I think in some cases, using lazy loading can actually be faster than pulling everything in doing a join multiply. The devil is always in the details. As a developer, you need to check the SQL that's being generated whether you are using lazy loading or not. One can only hope that EF Core will be more performant than EF 6. That was what Microsoft was saying, but, so far, the query translator seems like it is not very robust at all. In RC 1, there was a bug where it was using inner joins for everything, even non-required fields and giving incorrect results. So, I think it's going to be awhile before all the bugs get worked out and it gets to where EF 6 is today.

  • User profile image
    Jon

    As far as I can tell, running EF Core 1 on ASP.NET Web Forms with .NET Framework 4.6.1 doesn't work. I get a version error with regard to the immutable collections DLL. Works with a Console app, but, not a Web Forms app.

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.