Entity Framework Articles

EntityFramework Core can write incredibly complex queries for you, with great ease, most of the time. However, for complex situations, it may be necessary to create views to help ensure that you get the right data, in the right structure, and at the right time. Let's dive into this process and how to approach the situation with a structured process that is repeatable.

I'm a huge fan of Entity Framework Migrations, using them for almost all client projects. In a given week, I will see dozens of changes deploy to production successfully across our portfolio of projects. However, there is always that "one task" that results in a failure and each time it happens it triggers an update to our internal training and review processes, and it has to do with repeatable scripting and the use of the "idempotent" flag. I thought I'd share our experiences with everyone, to help prevent issues for others.

Projects can evolve over time, and the history of granular migrations within Entity Framework can result in a bloated change history. Additionally, changes can occur within Entity Framework tooling that may result in code warnings or other similar concerns. Resetting your migrations to squash the history can be a very helpful process, however it requires precision and care.

I love Entity Framework Core; I do; however, it can sometimes make me want to pull my hair out. Renaming tables is one of those situations for sure, but it can be easy to manage with a bit of planning.

Often times Entity Framework is thrown under the bus as a poor performer, in this post I share my experience of things that I've encountered with quick code changes to get great performance.

The larger your project gets, the more complicated the Entity Framework setup becomes. This post explores a few techniques to improve the management of complex projects.

We would all love to work with only new development, however, we know that isn't possible. Although we might be working with legacy code, or databases we can still work to leverage new technology even if bound by old semantics and standards.

Entity Framework is an amazingly powerful tool, however, there are times that you can confuse the tooling with catastrophic results. One of these times is with a change to a namespace or class, let's explore how to resolve these issues.